From: Namhyung Kim <namhyung@gmail.com>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] Staging: use DEFINE_PCI_DEVICE_TABLE when possible
Date: Fri, 10 Dec 2010 01:40:24 +0900 [thread overview]
Message-ID: <1291912830-13151-1-git-send-email-namhyung@gmail.com> (raw)
Hi,
This patchset tries to convert open-coded struct pci_device_id tables
to preferred form of DEFINE_PCI_DEVICE_TABLE. As a result it will make
the tables const and marks as __devinitconst.
Being conservative, I only convert the tables already declared as const
but it could be applied to others too. I'll prepare another series for
those if this looks good to you.
Thanks.
---
Only compile-tested!
Namhyung Kim (6):
Staging: sm7xx: use DEFINE_PCI_DEVICE_TABLE
Staging: cx25821: use DEFINE_PCI_DEVICE_TABLE
Staging: rtl8192e: use DEFINE_PCI_DEVICE_TABLE
Staging: phison: use DEFINE_PCI_DEVICE_TABLE
Staging: vme_tsi148: use DEFINE_PCI_DEVICE_TABLE
Staging: vme_ca91cx42: use DEFINE_PCI_DEVICE_TABLE
drivers/staging/cx25821/cx25821-alsa.c | 2 +-
drivers/staging/phison/phison.c | 2 +-
drivers/staging/rtl8192e/r8192E_core.c | 2 +-
drivers/staging/sm7xx/smtcfb.c | 2 +-
drivers/staging/vme/bridges/vme_ca91cx42.c | 2 +-
drivers/staging/vme/bridges/vme_tsi148.c | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
--
1.7.3.3.400.g93cef
next reply other threads:[~2010-12-09 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 16:40 Namhyung Kim [this message]
2010-12-09 16:40 ` [PATCH 1/6] Staging: sm7xx: use DEFINE_PCI_DEVICE_TABLE Namhyung Kim
2010-12-09 16:40 ` [PATCH 2/6] Staging: cx25821: " Namhyung Kim
2010-12-09 16:40 ` [PATCH 3/6] Staging: rtl8192e: " Namhyung Kim
2010-12-09 16:40 ` [PATCH 4/6] Staging: phison: " Namhyung Kim
2010-12-09 16:40 ` [PATCH 5/6] Staging: vme_tsi148: " Namhyung Kim
2010-12-09 16:40 ` [PATCH 6/6] Staging: vme_ca91cx42: " Namhyung Kim
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=1291912830-13151-1-git-send-email-namhyung@gmail.com \
--to=namhyung@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.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