summaryrefslogtreecommitdiffstats
path: root/Documentation/security
diff options
context:
space:
mode:
authorJoe Perches <joe@perches.com>2019-09-06 23:11:51 +0200
committerJonathan Corbet <corbet@lwn.net>2019-09-14 09:57:43 +0200
commitcbacb5ab0aa04a49030e520523ef9405c9cafa95 (patch)
treed6510fd81b033ca31bc593247656c0617fd75a2f /Documentation/security
parentDocumentation: Add "earlycon=sbi" to the admin guide (diff)
downloadlinux-cbacb5ab0aa04a49030e520523ef9405c9cafa95.tar.xz
linux-cbacb5ab0aa04a49030e520523ef9405c9cafa95.zip
docs: printk-formats: Stop encouraging use of unnecessary %h[xudi] and %hh[xudi]
Standard integer promotion is already done and %hx and %hhx is useless so do not encourage the use of %hh[xudi] or %h[xudi]. As Linus said in: https://lore.kernel.org/lkml/CAHk-=wgoxnmsj8GEVFJSvTwdnWm8wVJthefNk2n6+4TC=20e0Q@mail.gmail.com/ It's a pointless warning, making for more complex code, and making people remember esoteric printf format details that have no reason for existing. The "h" and "hh" things should never be used. The only reason for them being used if if you have an "int", but you want to print it out as a "char" (and honestly, that is a really bad reason, you'd be better off just using a proper cast to make the code more obvious). So if what you have a "char" (or unsigned char) you should always just print it out as an "int", knowing that the compiler already did the proper type conversion. Signed-off-by: Joe Perches <joe@perches.com> Reviewed-by: Louis Taylor <louis@kragniz.eu> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/security')
0 files changed, 0 insertions, 0 deletions