From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v2 0/2] lib/vsprintf: introduce stricter rules for %p extensions
Date: Tue, 29 Dec 2015 18:42:36 +0200 [thread overview]
Message-ID: <1451407358-7041-1-git-send-email-andriy.shevchenko@linux.intel.com> (raw)
Besides the code refactoring we introduce the following rules for %p extensions
here. i.e:
- fixed type extensions are always printed in hex format, prefixed by '0x',
small letters, full field width on a running architecture (%pa[dp], %pNF)
- fallback to %p based on different kernel configuration will be under the same
rule set as for fixed types above (%pCn when COMMON_CLK=n, %p[FfSsB] when
KALLSYMS=n)
- fallback to %p of unimplemented extension will be under the same rule set as
for fixed types above (%pN)
Since v1:
- address comments from Joe and Rasmums (might be not all of them)
- add patch 2
- desribe in cover letter what is done besides refactoring
Andy Shevchenko (2):
lib/vsprintf: refactor duplicate code to special_hex_number()
lib/vsprintf: factor out %pN[F] handler as netdev_bits()
lib/vsprintf.c | 70 ++++++++++++++++++++++++++++++++--------------------------
1 file changed, 39 insertions(+), 31 deletions(-)
--
2.6.4
next reply other threads:[~2015-12-29 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 16:42 Andy Shevchenko [this message]
2015-12-29 16:42 ` [PATCH v2 1/2] lib/vsprintf: refactor duplicate code to special_hex_number() Andy Shevchenko
2015-12-29 16:42 ` [PATCH v2 2/2] lib/vsprintf: factor out %pN[F] handler as netdev_bits() 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=1451407358-7041-1-git-send-email-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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