From: Maurizio Lombardi <mlombard@redhat.com>
To: tj@kernel.org
Cc: joe@perches.com, linux@rasmusvillemoes.dk, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/3] fix *pbl format support
Date: Wed, 16 Sep 2015 11:08:40 +0200 [thread overview]
Message-ID: <1442394523-19176-1-git-send-email-mlombard@redhat.com> (raw)
Hi,
I tried to fix the "*pb[l]" format issue while taking care of the problems
discussed in this thread:
https://lkml.org/lkml/2015/9/9/153
I would like to know whether this approach is more acceptable to you:
PATCH 1 modifies the code so that the printf_spec struct is not passed by value
anymore, instead a const pointer is used and the structure is copied to
a local variable only when necessary.
PATCH 2 modifies the bitmap_*_string() functions so they'll append "..." to the
output string whenever the buffer is not sufficiently large.
example of output:
*pb: cccccccc,...
*pbl: 1-2,5-7,...
PATCH 3 increases the size of printf_spec.field_width (from s16 to s32).
Maurizio Lombardi (3):
lib/vsprintf.c: Do not pass printf_spec by value on stack.
lib/vsprintf.c: append "..." if the *pb[l] output has been truncated.
lib/vsprintf.c: increase the size of the field_width variable
lib/vsprintf.c | 275 +++++++++++++++++++++++++++++++++++----------------------
1 file changed, 167 insertions(+), 108 deletions(-)
--
Maurizio Lombardi
next reply other threads:[~2015-09-16 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 9:08 Maurizio Lombardi [this message]
2015-09-16 9:08 ` [RFC PATCH 1/3] lib/vsprintf.c: Do not pass printf_spec by value on stack Maurizio Lombardi
2015-09-16 9:08 ` [RFC PATCH 2/3] lib/vsprintf.c: append "..." if the *pb[l] output has been truncated Maurizio Lombardi
2015-09-16 9:08 ` [RFC PATCH 3/3] lib/vsprintf.c: increase the size of the field_width variable Maurizio Lombardi
2015-09-16 12:27 ` [RFC PATCH 0/3] fix *pbl format support Rasmus Villemoes
2015-09-16 12:53 ` Maurizio Lombardi
2015-09-16 17:45 ` Tejun Heo
2015-09-16 20:35 ` Rasmus Villemoes
2015-09-21 14:54 ` Maurizio Lombardi
2015-09-21 16:24 ` Rasmus Villemoes
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=1442394523-19176-1-git-send-email-mlombard@redhat.com \
--to=mlombard@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=tj@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).