From: Greg KH <greg@kroah.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: devel@linuxdriverproject.org, Joe Perches <joe@perches.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
devel@driverdev.osuosl.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
gregkh@suse.de, support@sbei.com,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, support@onestopsystems.com
Subject: Re: [PATCH -next] staging/cxt1e1: Convert bare printks to pr_<level>
Date: Wed, 5 May 2010 09:21:01 -0700 [thread overview]
Message-ID: <20100505162101.GA12809@kroah.com> (raw)
In-Reply-To: <201005051421.14647.PeterHuewe@gmx.de>
On Wed, May 05, 2010 at 02:21:14PM +0200, Peter Hüwe wrote:
> Am Montag 03 Mai 2010 21:33:16 schrieb Joe Perches:
> > Added #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> > A few line splits for long arguments
> > A couple of embedded function names converted to "%s", __func__
> > Removed some uses of THIS_MODULE->name
> >
> > Signed-off-by: Joe Perches <joe@perches.com>
>
> Hi,
> I applied Joe's patch, but unfortunately it misses out one part of Randy's
> original patch, i.e. the conversion in line 286 of hwprobe.c.
>
> Joe: Can you perhaps add this to your patch?
I've already applied Joe's patch, so I'll queue up yours as well.
thanks,
greg k-h
prev parent reply other threads:[~2010-05-05 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 5:16 linux-next: Tree for May 3 Stephen Rothwell
2010-05-03 17:06 ` [PATCH -next] power: fix block_io.c printk warning Randy Dunlap
2010-05-03 22:00 ` Rafael J. Wysocki
[not found] ` <20100503151619.f75e3a80.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-05-03 17:07 ` [PATCH -next] usbserial: fix mos7720 dependencies Randy Dunlap
2010-05-03 17:09 ` [PATCH -next] staging: fix cxt1e1 module names Randy Dunlap
2010-05-03 18:02 ` Joe Perches
2010-05-03 18:06 ` Randy Dunlap
2010-05-03 19:33 ` [PATCH -next] staging/cxt1e1: Convert bare printks to pr_<level> Joe Perches
2010-05-05 12:21 ` Peter Hüwe
2010-05-05 16:21 ` Greg KH [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=20100505162101.GA12809@kroah.com \
--to=greg@kroah.com \
--cc=PeterHuewe@gmx.de \
--cc=devel@driverdev.osuosl.org \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=support@onestopsystems.com \
--cc=support@sbei.com \
/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).