From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 1/1] lib/vsnprintf: Add %par specifier for sake of consistency
Date: Thu, 1 Dec 2016 03:43:43 +0200 [thread overview]
Message-ID: <20161201014343.23443-1-andriy.shevchenko@linux.intel.com> (raw)
While resource_size_t is repeating phys_addr_t, allocate %par specifier for
that type for sake of consistency.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
Documentation/printk-formats.txt | 13 ++++++++++---
lib/vsprintf.c | 11 +++++++++--
2 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt
index 5962949..d8c40c3 100644
--- a/Documentation/printk-formats.txt
+++ b/Documentation/printk-formats.txt
@@ -79,9 +79,16 @@ Physical addresses types phys_addr_t:
%pa[p] 0x01234567 or 0x0123456789abcdef
- For printing a phys_addr_t type (and its derivatives, such as
- resource_size_t) which can vary based on build options, regardless of
- the width of the CPU data path. Passed by reference.
+ For printing a phys_addr_t type which can vary based on build options,
+ regardless of the width of the CPU data path. Passed by reference.
+
+Resource size types resource_size_t:
+
+ %par 0x01234567 or 0x0123456789abcdef
+
+ For printing a resource_size_t type which can vary based on build
+ options, regardless of the width of the CPU data path. Passed by
+ reference.
DMA addresses types dma_addr_t:
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index 0967771..c89c57d 100644
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
@@ -1373,6 +1373,10 @@ char *address_val(char *buf, char *end, const void *addr, const char *fmt)
num = *(const dma_addr_t *)addr;
size = sizeof(dma_addr_t);
break;
+ case 'r':
+ num = *(const resource_size_t *)addr;
+ size = sizeof(resource_size_t);
+ break;
case 'p':
default:
num = *(const phys_addr_t *)addr;
@@ -1548,8 +1552,11 @@ int kptr_restrict __read_mostly;
* N no separator
* The maximum supported length is 64 bytes of the input. Consider
* to use print_hex_dump() for the larger input.
- * - 'a[pd]' For address types [p] phys_addr_t, [d] dma_addr_t and derivatives
- * (default assumed to be phys_addr_t, passed by reference)
+ * - 'a[dpr]' For address types (default assumed to be phys_addr_t, passed by
+ * reference):
+ * [d] dma_addr_t
+ * [p] phys_addr_t
+ * [r] resource_size_t
* - 'd[234]' For a dentry name (optionally 2-4 last components)
* - 'D[234]' Same as 'd' but for a struct file
* - 'g' For block_device name (gendisk + partition number)
--
2.10.2
next reply other threads:[~2016-12-01 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 1:43 Andy Shevchenko [this message]
2016-12-27 11:41 ` [PATCH v1 1/1] lib/vsnprintf: Add %par specifier for sake of consistency Andy Shevchenko
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=20161201014343.23443-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).