linux-kernel - [PATCH 0/6] Staging: use DEFINE_PCI_DEVICE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1291912830-13151-1-git-send-email-namhyung@gmail.com>
Date:	Fri, 10 Dec 2010 01:40:24 +0900
From:	Namhyung Kim <namhyung@...il.com>
To:	Greg Kroah-Hartman <gregkh@...e.de>
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/6] Staging: use DEFINE_PCI_DEVICE_TABLE when possible

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/