[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170731075647.GB4316@linux-x5ow.site>
Date: Mon, 31 Jul 2017 09:56:47 +0200
From: Johannes Thumshirn <jthumshirn@...e.de>
To: Arvind Yadav <arvind.yadav.cs@...il.com>
Cc: martin.petersen@...cle.com, jejb@...ux.vnet.ibm.com, mdr@....com,
hare@...e.com, aacraid@...ptec.com, matthew@....cx,
fthain@...egraphics.com.au, schmitzmic@...il.com,
kashyap.desai@...adcom.com, sumit.saxena@...adcom.com,
gotom@...ian.or.jp, mrochs@...ux.vnet.ibm.com,
yokota@...lab.is.tsukuba.ac.jp, QLogic-Storage-Upstream@...ium.com,
jinpu.wang@...fitbricks.com, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/29] constify scsi pci_device_id.
On Sun, Jul 30, 2017 at 02:07:09PM +0530, Arvind Yadav wrote:
> pci_device_id are not supposed to change at runtime. All functions
> working with pci_device_id provided by <linux/pci.h> work with
> const pci_device_id. So mark the non-const structs as const.
Can't this go all in one patch instead of replicating the same patch 29
times?
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@...e.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
Powered by blists - more mailing lists