From: Joe Perches <joe@perches.com>
To: Richard Weinberger <richard@nod.at>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/4] UserModeLinux: Message logging neatening
Date: Wed, 14 May 2014 13:07:21 -0700 [thread overview]
Message-ID: <1400098041.30384.22.camel@joe-AO725> (raw)
In-Reply-To: <5373C996.7000409@nod.at>
On Wed, 2014-05-14 at 21:52 +0200, Richard Weinberger wrote:
> Am 10.05.2014 01:43, schrieb Joe Perches:
> > Joe Perches (4):
> > UserModeLinux: Convert UM_KERN_<LEVEL> to KERN_<LEVEL>
> > UserModeLinux: Remove unused #defines of UM_KERN_<LEVEL>
> > UserModeLinux: Use a more current logging style
> > UserModeLinux: Convert printks to pr_<level>
> Thank you Joe!
> I'll queue your patches for 3.16.
(adding Geert to cc's)
Hi Richard.
Please queue only patches 1 and 2.
Patches 3 and 4 are currently defective.
These need a bit of rework to compile appropriately.
I'll do what Al suggested below one day soon.
from: https://lkml.org/lkml/2012/9/29/106
On Sat, Sep 29, 2012 at 10:43 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Sat, Sep 29, 2012 at 10:27:44PM +0200, Geert Uytterhoeven wrote:
>> On Sat, Sep 29, 2012 at 10:10 PM, Joe Perches <joe@perches.com> wrote:
>> >> @@ -88,7 +88,7 @@ static int do_aio(aio_context_t ctx, enum aio_type type, int fd, char *buf,
>> >> iocbp->aio_nbytes = sizeof(c);
>> >> break;
>> >> default:
>> >> - printk(UM_KERN_ERR "Bogus op in do_aio - %d\n", type);
>> >> + printk(KERN_ERR "Bogus op in do_aio - %d\n", type);
>> >
>> > Maybe a follow-on patch to convert these to pr_<level>?
>>
>> That requires adding pr_<level> to arch/um/include/shared/user.h first.
>> Or to avoid duplication, extracting the pr_<level> definitions from
>> include/linux/printk.h to a new header file, and preincluding that one for
>> the user part of UML, too.
>
> Yecchhh.... Just how many of those pre-includes do you want to add?
> Seriously, if we get enough of those, it might make more sense to take
> them into a separate directory and add it to search paths, including
> that for userland objects of uml. If not, I'd rather copy them to
> include/generated in arch/um/Makefile and explicitly #include <generated/foo.h>
> them from user.h. It's trivially doable and as long as we have relatively
> few of those guys it's less PITA...
next prev parent reply other threads:[~2014-05-14 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 23:43 [uml-devel] [PATCH 0/4] UserModeLinux: Message logging neatening Joe Perches
2014-05-09 23:43 ` [uml-devel] [PATCH 1/4] UserModeLinux: Convert UM_KERN_<LEVEL> to KERN_<LEVEL> Joe Perches
2014-05-12 7:59 ` Geert Uytterhoeven
2014-05-09 23:43 ` [uml-devel] [PATCH 2/4] UserModeLinux: Remove unused #defines of UM_KERN_<LEVEL> Joe Perches
2014-05-09 23:43 ` [PATCH 3/4] UserModeLinux: Use a more current logging style Joe Perches
2014-05-09 23:43 ` [PATCH 4/4] UserModeLinux: Convert printks to pr_<level> Joe Perches
2014-05-14 19:52 ` [PATCH 0/4] UserModeLinux: Message logging neatening Richard Weinberger
2014-05-14 20:07 ` Joe Perches [this message]
2014-05-14 20:12 ` Richard Weinberger
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=1400098041.30384.22.camel@joe-AO725 \
--to=joe@perches.com \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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