From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Joe Perches <joe@perches.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
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:57:32 +0100 [thread overview]
Message-ID: <4ACCC87C.5090800@tuffmail.co.uk> (raw)
In-Reply-To: <1254933396.2134.371.camel@Joe-Laptop.home>
Joe Perches wrote:
> On Wed, 2009-10-07 at 08:36 -0700, Linus Torvalds wrote:
>
>> On Wed, 7 Oct 2009, Alan Jenkins wrote:
>>
>>> We could fix this up, but it seems pointless. Callers don't really care
>>> about the extra characters added by printk(). Instead, let's return the
>>> length of the original message as formatted (and possibly truncated)
>>> by vscnprintf().
>>>
>> Or we could just change it to 'void'. As Joe Perches says, nobody really
>> cares deeply enough for this to generally even matter.
>>
>
> Here are changes to make printk/vprintk return void
> to the only uses I found:
>
> arch/arm/mach-iop13xx/pci.c | 2 +-
> arch/arm/mach-iop13xx/setup.c | 2 +-
> drivers/char/mem.c | 6 ++----
> drivers/md/md.c | 3 +--
> drivers/md/raid5.c | 3 ++-
> drivers/net/e100.c | 9 +++++----
> include/linux/kernel.h | 16 ++++++++--------
> include/net/sctp/sctp.h | 6 +++---
> kernel/lockdep.c | 4 ++--
> kernel/printk.c | 10 +++-------
> net/sunrpc/svc.c | 9 +++------
> 11 files changed, 31 insertions(+), 39 deletions(-)
>
Ok, you beat me to it.
My second patch will depend on this. Two questions -
- May I add it to my series with your Signed-off-by?
- May I split it up, so I can CC individual maintainers with the
revelant portions?
Thanks
Alan
next prev parent reply other threads:[~2009-10-07 16:58 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
2009-10-07 16:36 ` Joe Perches
2009-10-07 16:57 ` Alan Jenkins [this message]
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=4ACCC87C.5090800@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=joe@perches.com \
--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
Powered by JetHome