From: Joe Perches <joe@perches.com>
To: Greg KH <greg@kroah.com>
Cc: Axel Lin <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>,
Alex Dubov <oakad@yahoo.com>,
David Altobelli <david.altobelli@hp.com>,
Brent Casavant <bcasavan@sgi.com>,
J Freyensee <james_p_freyensee@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] MISC: Convert to DEFINE_PCI_DEVICE_TABLE
Date: Fri, 02 Dec 2011 13:01:48 -0800 [thread overview]
Message-ID: <1322859708.17683.17.camel@joe2Laptop> (raw)
In-Reply-To: <20111202160326.GA13819@kroah.com>
On Fri, 2011-12-02 at 08:03 -0800, Greg KH wrote:
> On Fri, Dec 02, 2011 at 11:02:57AM +0800, Axel Lin wrote:
> > Convert static struct pci_device_id *[] to static DEFINE_PCI_DEVICE_TABLE
> > tables. Also convert to the PCI_DEVICE/PCI_VDEVICE macros for better
> > readablity.
[]
> > diff --git a/drivers/misc/hpilo.c b/drivers/misc/hpilo.c
[]
> > @@ -828,7 +828,7 @@ out:
> > return error;
> > }
> >
> > -static struct pci_device_id ilo_devices[] = {
> > +static DEFINE_PCI_DEVICE_TABLE(ilo_devices) = {
>
> No, I hate this macro, see, it's actually taking you more characters to
> use it than to just properly define the structure yourself. It's
> pointless and stupid.
Not quite.
include/linux/pci.h:#define DEFINE_PCI_DEVICE_TABLE(_table) \
include/linux/pci.h- const struct pci_device_id _table[] __devinitconst
Using the macro does declare the struct const and
use attribute __devinitconst to place the table into
section .devinit.rodata.
The straight definition does not.
> So no, I'm not going to accept this patch, sorry.
Never in doubt, not always right...
cheers, Joe
next prev parent reply other threads:[~2011-12-02 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 3:02 [PATCH] MISC: Convert to DEFINE_PCI_DEVICE_TABLE Axel Lin
2011-12-02 15:42 ` Brent Casavant
2011-12-02 15:50 ` Altobelli, David
2011-12-02 16:03 ` Greg KH
2011-12-02 21:01 ` Joe Perches [this message]
2011-12-03 1:04 ` Axel Lin
2011-12-03 1:11 ` 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=1322859708.17683.17.camel@joe2Laptop \
--to=joe@perches.com \
--cc=arnd@arndb.de \
--cc=axel.lin@gmail.com \
--cc=bcasavan@sgi.com \
--cc=david.altobelli@hp.com \
--cc=greg@kroah.com \
--cc=james_p_freyensee@linux.intel.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.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