From: Frederic Weisbecker <fweisbec@gmail.com>
To: "André Goddard Rosa" <andre.goddard@gmail.com>
Cc: laijs@cn.fujitsu.com, mingo@elte.hu, davem@davemloft.net,
akpm@linux-foundation.org, harvey.harrison@gmail.com,
linux list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/7] vsprintf: reduce code size and clean up
Date: Mon, 2 Nov 2009 21:12:34 +0100 [thread overview]
Message-ID: <20091102201232.GE4880@nowhere> (raw)
In-Reply-To: <b8bf37780911020926v20ebfcc0nc0b0712875bbb875@mail.gmail.com>
On Mon, Nov 02, 2009 at 03:26:07PM -0200, André Goddard Rosa wrote:
> Subject: [PATCH v2 0/7] vsprintf: reduce code size and clean up
>
> This patch reduces code size by 240 bytes on my Core 2 with gcc 4.4.1:
> text data bss dec hex filename
> 15767 0 8 15775 3d9f lib/vsprintf.o-before
> 15527 0 8 15535 3caf lib/vsprintf.o-after
>
> and implements some cleanups.
>
> Changelog:
> v2: addressed feedback from Frederic Weisbecker review (thanks!!)
> and split into separate patches
> v1: original submission
>
> André Goddard Rosa (7):
> vsprintf: factorize "(null)" string
> vsprintf: pre-calculate final string length
> vsprintf: give it some care to please checkpatch.pl
> vsprintf: use TOLOWER whenever possible
> vsprintf: reduce code size by avoiding extra check
> vsprintf: move local vars to block local vars and remove unneeded
> ones
> vsprintf: factor out skip_space code in a separate function
>
> lib/vsprintf.c | 306 ++++++++++++++++++++++++++++++--------------------------
> 1 files changed, 163 insertions(+), 143 deletions(-)
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
But please add a more verbose changelog in the 5th as per Ingo's
request, and do the case statement merge I suggested in the 6th.
Thanks!
prev parent reply other threads:[~2009-11-02 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 17:26 [PATCH v2 0/7] vsprintf: reduce code size and clean up André Goddard Rosa
2009-11-02 20:12 ` Frederic Weisbecker [this message]
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=20091102201232.GE4880@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andre.goddard@gmail.com \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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