From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, greg@kroah.com
Subject: Re: [PATCH 0/4] Introduce and use printk pointer extension %pV
Date: Wed, 30 Jun 2010 13:07:09 -0700 (PDT) [thread overview]
Message-ID: <20100630.130709.93452021.davem@davemloft.net> (raw)
In-Reply-To: <cover.1277636090.git.joe@perches.com>
From: Joe Perches <joe@perches.com>
Date: Sun, 27 Jun 2010 04:02:32 -0700
> Recursive printk can reduce the total image size of an x86 defconfig about 1%
> by reducing duplicated KERN_<level> strings and centralizing the functions
> used by macros in new separate functions.
>
> Joe Perches (4):
> vsprintf: Recursive vsnprintf: Add "%pV", struct va_format
> device.h drivers/base/core.c Convert dev_<level> logging macros to functions
> netdevice.h net/core/dev.c: Convert netdev_<level> logging macros to functions
> netdevice.h: Change netif_<level> macros to call netdev_<level> functions
I'm fine with this, thanks Joe.
Greg, could you ACK this and let me know if it's OK if it swings
through my net-next-2.6 tree?
Thanks.
next prev parent reply other threads:[~2010-06-30 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 11:02 [PATCH 0/4] Introduce and use printk pointer extension %pV Joe Perches
2010-06-27 11:02 ` [PATCH 1/4] vsprintf: Recursive vsnprintf: Add "%pV", struct va_format Joe Perches
2010-06-27 11:02 ` [PATCH 2/4] device.h drivers/base/core.c Convert dev_<level> logging macros to functions Joe Perches
2010-06-27 11:02 ` [PATCH 3/4] netdevice.h net/core/dev.c: Convert netdev_<level> " Joe Perches
2010-06-27 11:02 ` [PATCH 4/4] netdevice.h: Change netif_<level> macros to call netdev_<level> functions Joe Perches
2010-06-30 20:07 ` David Miller [this message]
2010-07-03 5:32 ` [PATCH 0/4] Introduce and use printk pointer extension %pV David Miller
2010-07-03 16:08 ` Greg KH
2010-07-04 17:40 ` David Miller
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=20100630.130709.93452021.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).