From: Joe Perches <joe@perches.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] include/linux/kernel.h: Move logging bits to include/linux/logging.h
Date: Tue, 09 Nov 2010 12:10:13 -0800 [thread overview]
Message-ID: <1289333413.28590.29.camel@Joe-Laptop> (raw)
In-Reply-To: <20101109200118.GA13016@core2.telecom.by>
On Tue, 2010-11-09 at 22:01 +0200, Alexey Dobriyan wrote:
> On Tue, Nov 09, 2010 at 10:49:19AM -0800, Linus Torvalds wrote:
> > On Tue, Nov 9, 2010 at 10:43 AM, Joe Perches <joe@perches.com> wrote:
> > >
> > > diff from V1 - Don't add pr_<level>_once macros
> > >
> > > include/linux/kernel.h | 244 +--------------------------------------
> > > include/linux/logging.h | 295 +++++++++++++++++++++++++++++++++++++++++++++++
> > > 2 files changed, 296 insertions(+), 243 deletions(-)
> > > create mode 100644 include/linux/logging.h
> >
> > So where do the extra 53 lines come from now?
> >
> > This still is clearly not just code movement, and it's impossible for
> > me to see what actually changed. Something must have.
>
> Why linux_banner is moved?
> Why linux_proc_banner is moved?
It's only used by a printk.
> Why header is not named printk.h?
No particular reason nor any particular objection.
> Why random stuff like log_buf_kexec_setup() and hexdump is moved?
hexdump functions are logging message related
as is log_buf_kexec_setup.
hexdump should/will eventually have an
#ifdef CONFIG_PRINTK
external function prototypes
#else
static inline void
hex_dump_to_buffer(const void *buf, size_t len,
int rowsize, int groupsize,
char *linebuf, size_t linebuflen, bool ascii) {}
static inline void
print_hex_dump(const char *level, const char *prefix_str,
int prefix_type, int rowsize, int groupsize,
const void *buf, size_t len, bool ascii) {}
static inline void
print_hex_dump_bytes(const char *prefix_str, int prefix_type,
const void *buf, size_t len) {}
#endif
so the static strings of the call sites can be eliminated
when !CONFIG_PRINTK.
next prev parent reply other threads:[~2010-11-09 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 5:38 [PATCH] " Joe Perches
2010-11-09 18:23 ` Linus Torvalds
2010-11-09 18:43 ` [PATCH V2] " Joe Perches
2010-11-09 18:49 ` Linus Torvalds
2010-11-09 19:17 ` Joe Perches
2010-11-09 21:00 ` Ted Ts'o
2010-11-09 21:08 ` Joe Perches
2010-11-09 23:52 ` [PATCH V3] include/linux/kernel.h: Move logging bits to include/linux/printk.h Joe Perches
2010-11-09 20:01 ` [PATCH V2] include/linux/kernel.h: Move logging bits to include/linux/logging.h Alexey Dobriyan
2010-11-09 20:10 ` Joe Perches [this message]
2010-11-09 20:30 ` Joe Perches
2010-11-15 18:04 ` [PATCH V4] include/linux/kernel.h: Move logging bits to include/linux/printk.h Joe Perches
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=1289333413.28590.29.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome