[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6b6ba203-1352-26ed-8d7e-c14e7bb25d32@gmail.com>
Date: Mon, 31 Jul 2017 14:23:11 +0530
From: Arvind Yadav <arvind.yadav.cs@...il.com>
To: Johannes Thumshirn <jthumshirn@...e.de>
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 Monday 31 July 2017 01:26 PM, Johannes Thumshirn wrote:
> 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?
Yes, We can add all of them in single patch. But other maintainer wants
single single patch. thats why I have send 29 patch. :(
> Thanks,
> Johannes
>
~arvind
Powered by blists - more mailing lists