All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH 0/4] Introduce and use printk pointer extension %pV
Date: Sun, 27 Jun 2010 04:02:32 -0700	[thread overview]
Message-ID: <cover.1277636090.git.joe@perches.com> (raw)

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

 drivers/base/core.c       |   64 +++++++++++++++++++++++++
 include/linux/device.h    |  112 ++++++++++++++++++++++++++++++++++----------
 include/linux/kernel.h    |    5 ++
 include/linux/netdevice.h |   56 ++++++++++++----------
 lib/vsprintf.c            |    9 ++++
 net/core/dev.c            |   62 +++++++++++++++++++++++++
 6 files changed, 256 insertions(+), 52 deletions(-)


             reply	other threads:[~2010-06-27 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 11:02 Joe Perches [this message]
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 ` [PATCH 0/4] Introduce and use printk pointer extension %pV David Miller
2010-07-03  5:32   ` 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=cover.1277636090.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.