From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Johannes Weiner" <hannes-kernel@saeurebad.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init: Fix printk format strings
Date: Thu, 11 Oct 2007 21:15:35 +0200 [thread overview]
Message-ID: <19f34abd0710111215w7137c104p8205d562589f456b@mail.gmail.com> (raw)
In-Reply-To: <20071011172121.GC28048@saeurebad.de>
On 10/11/07, Johannes Weiner <hannes-kernel@saeurebad.de> wrote:
> On Thu, Oct 11, 2007 at 08:17:02AM +0200, Vegard Nossum wrote:
> > This makes sure printk format strings are string literals containing no
> > more than a single line.
>
> Perhaps you should write _why_ one-line printk()s are even needed, with
> profound reasons instead of constantly talking about mysterious later changes
> that you will propose any time soon.
In short, the reason for disallowing multiple lines per call is that
printk() will be less complex, while not really changing the
complexity of the callers (a change in the code, yes, but the changes
are trivial, and, actually, not that many).
I think I see now, though, that my changes will not gain support if I
do not lift this restriction.
You can find my current "mysterious later changes" as patches, with
descriptions, at this address: http://folk.uio.no/vegardno/xprintf/
Thanks for the tip, though. I am quite new to the kernel business, so
bear with me :)
Kind regards,
Vegard Nossum
prev parent reply other threads:[~2007-10-11 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 6:17 Vegard Nossum
2007-10-11 15:40 ` Randy Dunlap
2007-10-11 15:55 ` Vegard Nossum
2007-10-11 16:01 ` Randy Dunlap
2007-10-11 16:09 ` Vegard Nossum
2007-10-11 16:20 ` Randy Dunlap
2007-10-11 17:21 ` Johannes Weiner
2007-10-11 19:15 ` Vegard Nossum [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=19f34abd0710111215w7137c104p8205d562589f456b@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=hannes-kernel@saeurebad.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®