From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] printk: clean up return value
Date: Wed, 07 Oct 2009 17:25:07 +0100 [thread overview]
Message-ID: <4ACCC0E3.8050404@tuffmail.co.uk> (raw)
In-Reply-To: <alpine.LFD.2.01.0910070828190.3432@localhost.localdomain>
Linus Torvalds wrote:
> Hmm. I kind of agree with this, but at the same time I suspect that no
> caller should ever care about the loglevel characters (since they won't be
> _shown_), so your change still doesn't make it return a sensible value.
>
> So I get the feeling that you should also add a
>
> message_len -= 3;
>
> to the case where we peel off the "<.>" loglevel part at the head of the
> string. No?
>
The value is only really sensible for partial printk()s... except that
they're supposed to be prefixed with KERN_CONT. So yes, good point.
> Or we could just change it to 'void'. As Joe Perches says, nobody really
> cares deeply enough for this to generally even matter.
>
That involves more work, which explains why I shied away from it :-).
Ok, I'll do it.
Alan
next prev parent reply other threads:[~2009-10-07 16:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 8:39 printk: fix loglevels as used by x86 stack dump code Alan Jenkins
2009-10-07 8:39 ` [PATCH 1/7] printk: clean up return value Alan Jenkins
2009-10-07 13:55 ` Joe Perches
2009-10-07 15:36 ` Linus Torvalds
2009-10-07 16:25 ` Alan Jenkins [this message]
2009-10-07 16:36 ` Joe Perches
2009-10-07 16:57 ` Alan Jenkins
2009-10-07 17:42 ` Joe Perches
2009-10-07 8:39 ` [PATCH 2/7] kmsg: no need to limit the return value of printk Alan Jenkins
2009-10-07 8:39 ` [PATCH 3/7] printk: move the printing of the loglevel tag into a separate function Alan Jenkins
2009-10-07 8:39 ` [PATCH 4/7] printk: remove redundant test Alan Jenkins
2009-10-07 8:39 ` [PATCH 5/7] printk: fix printk(KERN_EMERG) followed by printk("emergency message\n") Alan Jenkins
2009-10-07 8:39 ` [PATCH 6/7] x86 dumpstack: fix printing of stack dump loglevels Alan Jenkins
2009-10-07 14:36 ` Linus Torvalds
2009-10-07 16:35 ` Alan Jenkins
2009-10-07 8:39 ` [PATCH 7/7] x86 dumpstack: fix log level of the first line in the stack dump Alan Jenkins
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=4ACCC0E3.8050404@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).