public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
	marek.vasut@gmail.com, richard@nod.at,
	cyrille.pitchen@wedev4u.fr, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] constify mtd pci_device_id
Date: Thu, 17 Aug 2017 15:02:43 +0200	[thread overview]
Message-ID: <20170817150243.38d1db3f@bbrezillon> (raw)
In-Reply-To: <1501777330-21380-1-git-send-email-arvind.yadav.cs@gmail.com>

Le Thu,  3 Aug 2017 21:52:04 +0530,
Arvind Yadav <arvind.yadav.cs@gmail.com> a écrit :

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

Applied the whole series to l2-mtd/master.

Thanks,

Boris

> 
> Arvind Yadav (6):
>   [PATCH 1/6] mtd: maps: ichxrom: constify pci_device_id.
>   [PATCH 2/6] mtd: amd76xrom: constify pci_device_id.
>   [PATCH 3/6] mtd: esb2rom: constify pci_device_id.
>   [PATCH 4/6] mtd: ck804xrom: constify pci_device_id.
>   [PATCH 5/6] mtd: intel_vr_nor: constify pci_device_id.
>   [PATCH 6/6] mtd: pci: constify pci_device_id.
> 
>  drivers/mtd/maps/amd76xrom.c    | 4 ++--
>  drivers/mtd/maps/ck804xrom.c    | 4 ++--
>  drivers/mtd/maps/esb2rom.c      | 4 ++--
>  drivers/mtd/maps/ichxrom.c      | 4 ++--
>  drivers/mtd/maps/intel_vr_nor.c | 2 +-
>  drivers/mtd/maps/pci.c          | 2 +-
>  6 files changed, 10 insertions(+), 10 deletions(-)
> 

      parent reply	other threads:[~2017-08-17 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 16:22 [PATCH 0/6] constify mtd pci_device_id Arvind Yadav
2017-08-03 16:22 ` [PATCH 1/6] mtd: ichxrom: constify pci_device_id Arvind Yadav
2017-08-03 16:22 ` [PATCH 2/6] mtd: amd76xrom: " Arvind Yadav
2017-08-03 16:22 ` [PATCH 3/6] mtd: esb2rom: " Arvind Yadav
2017-08-03 16:22 ` [PATCH 4/6] mtd: ck804xrom: " Arvind Yadav
2017-08-03 16:22 ` [PATCH 5/6] mtd: intel_vr_nor: " Arvind Yadav
2017-08-03 16:22 ` [PATCH 6/6] mtd: pci: " Arvind Yadav
2017-08-17 13:02 ` Boris Brezillon [this message]

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=20170817150243.38d1db3f@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=richard@nod.at \
    /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