From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH v1 2/2] docs: printk-formats: Treat char as always unsigned
Date: Mon, 3 Jul 2023 17:58:39 +0300 [thread overview]
Message-ID: <20230703145839.14248-2-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20230703145839.14248-1-andriy.shevchenko@linux.intel.com>
The Linux kernel switched to have char be equivalent to usigned char.
Reflect this in the printk specifiers.
Fixes: 3bc753c06dd0 ("kbuild: treat char as always unsigned")
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
Documentation/core-api/printk-formats.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/core-api/printk-formats.rst b/Documentation/core-api/printk-formats.rst
index 2f3a6e0b3fc4..4451ef501936 100644
--- a/Documentation/core-api/printk-formats.rst
+++ b/Documentation/core-api/printk-formats.rst
@@ -15,8 +15,9 @@ Integer types
If variable is of Type, use printk format specifier:
------------------------------------------------------------
- char %d or %hhx
+ signed char %d or %hhx
unsigned char %u or %x
+ char %u or %x
short int %d or %hx
unsigned short int %u or %x
int %d or %x
--
2.40.0.1.gaa8946217a0b
next prev parent reply other threads:[~2023-07-03 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 14:58 [PATCH v1 1/2] docs: printk-formats: Fix hex printing of signed values Andy Shevchenko
2023-07-03 14:58 ` Andy Shevchenko [this message]
2023-07-14 15:34 ` [PATCH v1 2/2] docs: printk-formats: Treat char as always unsigned Petr Mladek
2023-07-14 16:04 ` Andy Shevchenko
2023-07-18 11:46 ` Petr Mladek
2023-07-03 15:08 ` [PATCH v1 1/2] docs: printk-formats: Fix hex printing of signed values Andy Shevchenko
2023-07-14 15:32 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230703145839.14248-2-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox