From: Ingo Molnar <mingo@elte.hu>
To: Nick Andrew <nick@nick-andrew.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
joe@perches.com
Subject: Re: [PATCH 1/2] printk: Refactor processing of line severity tokens
Date: Mon, 14 Apr 2008 09:58:34 +0200 [thread overview]
Message-ID: <20080414075834.GK16163@elte.hu> (raw)
In-Reply-To: <20080413122342.31769.40091.stgit@marcab.local.tull.net>
* Nick Andrew <nick@nick-andrew.net> wrote:
> printk: Refactor processing of line severity tokens
>
> Restructure the logic of vprintk() so the processing of the leading 3
> characters of each input line is in one place, regardless whether
> printk_time is enabled. This makes the code smaller and easier to
> understand.
thanks, applied - nice cleanup!
i also added the size stats:
text data bss dec hex filename
6157 397 1049804 1056358 101e66 printk.o.before
6117 397 1049804 1056318 101e3e printk.o.after
Ingo
next prev parent reply other threads:[~2008-04-14 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 11:53 Nick Andrew
2008-04-13 11:54 ` [PATCH 2/2] printk: Remember the message level for multi-line output Nick Andrew
2008-04-13 12:26 ` [PATCH 1/2] printk: Refactor processing of line severity tokens Nick Andrew
2008-04-14 7:58 ` Ingo Molnar [this message]
2008-04-13 12:27 ` [PATCH 2/2] printk: Remember the message level for multi-line output Nick Andrew
2008-04-14 8:03 ` Ingo Molnar
2008-04-14 10:12 ` Nick Andrew
2008-04-14 10:26 ` Ingo Molnar
2008-04-14 11:03 ` Nick Andrew
2008-04-14 11:43 ` Johannes Weiner
2008-04-14 12:21 ` Ingo Molnar
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=20080414075834.GK16163@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@nick-andrew.net \
--cc=tglx@linutronix.de \
--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