From: Randy Dunlap <randy.dunlap@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
gregkh@suse.de, devel@driverdev.osuosl.org,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
support@sbei.com, support@onestopsystems.com
Subject: Re: [PATCH -next] staging: fix cxt1e1 module names
Date: Mon, 3 May 2010 11:06:57 -0700 [thread overview]
Message-ID: <20100503110657.00b4e140.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1272909764.30040.92.camel@Joe-Laptop.home>
On Mon, 03 May 2010 11:02:44 -0700 Joe Perches wrote:
> On Mon, 2010-05-03 at 10:09 -0700, Randy Dunlap wrote:
> > From: Randy Dunlap <randy.dunlap@oracle.com>
> >
> > Lots of cxt1e1 source code uses THIS_MODULE->name, which won't build
> > when CONFIG_MODULES is not enabled, so use KBUILD_MODNAME instead.
>
> Perhaps a conversion to pr_<level> is better?
Sure, fine with me. Thanks.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-03 18:11 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 [this message]
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
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=20100503110657.00b4e140.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).