linux-kernel - Re: [PATCH 0/25] Replace 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1405700934.605.31.camel@jarvis.lan>
Date:	Fri, 18 Jul 2014 09:28:54 -0700
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Benoit Taine <benoit.taine@...6.fr>
Cc:	linux-pci@...r.kernel.org, ath5k-devel@...ema.h4ckr.net,
	ath9k-devel@...ema.h4ckr.net, linux-hippi@...site.dk,
	dri-devel@...ts.freedesktop.org, linux-acenic@...site.dk,
	wil6210@....qualcomm.com, platform-driver-x86@...r.kernel.org,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, linux-wireless@...r.kernel.org,
	linux-mips@...ux-mips.org, users@...x00.serialmonkey.com,
	linux-rdma@...r.kernel.org,
	virtualization@...ts.linux-foundation.org,
	industrypack-devel@...ts.sourceforge.net,
	linux-can@...r.kernel.org, linux-mmc@...r.kernel.org,
	linux-fbdev@...r.kernel.org, ath10k@...ts.infradead.org,
	linux-crypto@...r.kernel.org, MPT-FusionLinux.pdl@...gotech.com,
	devel@...uxdriverproject.org, xen-devel@...ts.xenproject.org,
	linux-pcmcia@...ts.infradead.org, e1000-devel@...ts.sourceforge.net
Subject: Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use

On Fri, 2014-07-18 at 17:26 +0200, Benoit Taine wrote:
> We should prefer `const struct pci_device_id` over
> `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines.
> This issue was reported by checkpatch.

What kernel coding style?  checkpatch isn't the arbiter of style, if
that's the only problem.

The DEFINE_PCI macro was a well reasoned addition when it was added in
2008.  The problem was most people were getting the definition wrong.
When we converted away from CONFIG_HOTPLUG, having this DEFINE_ meant
that only one place needed changing instead of hundreds for PCI tables.

The reason people were getting the PCI table wrong was mostly the init
section specifiers which are now gone, but it has enough underlying
utility (mostly constification) that I don't think we'd want to churn
the kernel hugely to make a change to struct pci_table and then have to
start detecting and fixing misuses.

James

--
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/