From: Jesper Juhl <jesper.juhl@gmail.com>
To: Arthur Othieno <a.othieno@bluewin.ch>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] small cleanup for kernel/printk.c - CodingStyle, Whitespace, printk() loglevels...
Date: Thu, 6 Oct 2005 01:41:53 +0200 [thread overview]
Message-ID: <9a8748490510051641m11f554efn5ef13e4fdecbc442@mail.gmail.com> (raw)
In-Reply-To: <20051005220900.GA2559@mars>
On 10/6/05, Arthur Othieno <a.othieno@bluewin.ch> wrote:
> On Wed, Oct 05, 2005 at 11:56:49PM +0200, Jesper Juhl wrote:
> > Small CodingStyle cleanup for kernel/printk.c
> > Removes some trailing whitespace
> > Breaks long lines and make other small changes to conform to CodingStyle
> > Add explicit printk loglevels in two places.
> >
> > Linus: Sorry to Cc: you on something as trivial as this, but you /are/ listed as
> > the author of the file and I couldn't find a relevant maintainer (except for
> > perhaps Andrew (so I added him to CC as well)).
> >
> >
> > Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
> > ---
> >
> > Patch has been compile tested.
> >
> > kernel/printk.c | 78 ++++++++++++++++++++++++++++++--------------------------
> > 1 files changed, 42 insertions(+), 36 deletions(-)
> >
> > --- linux-2.6.14-rc3-git5-orig/kernel/printk.c 2005-10-03 21:55:39.000000000 +0200
> > +++ linux-2.6.14-rc3-git5/kernel/printk.c 2005-10-05 23:46:54.000000000 +0200
> > @@ -169,11 +169,11 @@ static int __init log_buf_len_setup(char
> > size = roundup_pow_of_two(size);
> > if (size > log_buf_len) {
> > unsigned long start, dest_idx, offset;
> > - char * new_log_buf;
> > + char *new_log_buf;
> >
> > new_log_buf = alloc_bootmem(size);
> > if (!new_log_buf) {
> > - printk("log_buf_len: allocation failed\n");
> > + printk(KERN_WARNING "log_buf_len: allocation failed\n");
>
> Wouldn't KERN_ERR be more appropriate here?
I don't think so. Things will still work.
Personally I consider this a warning condition, and without an
explicit loglevel that's also what it was logged as in the past, so
this changes nothing.
If other people disagree I can modify the patch, sure, but I think
KERN_WARNING is appropriate.
[snip]
> > - struct console *a,*b;
> > + struct console *a, *b;
> > int res = 1;
>
> Beep! :)
>
huh?
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-10-05 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 21:56 Jesper Juhl
2005-10-05 22:09 ` Arthur Othieno
2005-10-05 23:41 ` Jesper Juhl [this message]
2005-10-06 0:09 ` Arthur Othieno
2005-10-06 0:33 ` Jesper Juhl
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=9a8748490510051641m11f554efn5ef13e4fdecbc442@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=a.othieno@bluewin.ch \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®