From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: paulus@samba.org, benh@kernel.crashing.org, adaplas@gmail.com,
mbroemme@libmpq.org, FlorianSchandinat@gmx.de,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/28] constify fbdev pci_device_id.
Date: Tue, 01 Aug 2017 15:37:45 +0000 [thread overview]
Message-ID: <3297262.0f1bRl44hx@amdc3058> (raw)
In-Reply-To: <1500572393-18844-1-git-send-email-arvind.yadav.cs@gmail.com>
On Thursday, July 20, 2017 11:09:25 PM 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.
Patches #1-28 queued for 4.14, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2017-08-01 15:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170720174007epcas3p2b1560c96711fde38a06d74d24493f952@epcas3p2.samsung.com>
2017-07-20 17:51 ` [PATCH 00/28] constify fbdev pci_device_id Arvind Yadav
2017-07-20 17:51 ` [PATCH 01/28] video: fbdev: radeon: constify pci_device_id Arvind Yadav
2017-07-20 17:51 ` [PATCH 02/28] video: fbdev: atyfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 03/28] video: fbdev: aty128fb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 04/28] video: fbdev: sunxvr2500: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 05/28] video: fbdev: asiliantfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 06/28] video: fbdev: intelfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 07/28] video: fbdev: pvr2fb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 08/28] video: fbdev: tridentfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 09/28] video: fbdev: skeletonfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 10/28] video: fbdev: via: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 11/28] video: fbdev: savage: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 12/28] video: fbdev: riva: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 13/28] video: fbdev: i810: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 14/28] video: fbdev: arkfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 15/28] video: fbdev: kyro: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 16/28] video: fbdev: vermilion: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 17/28] video: fbdev: nvidia: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 18/28] video: fbdev: mb862xx: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 19/28] video: fbdev: tdfx: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 20/28] video: fbdev: sunxvr500: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 21/28] video: fbdev: imsttfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 22/28] video: fbdev: pm2fb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 23/28] video: fbdev: gxfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 24/28] video: fbdev: neofb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 25/28] video: fbdev: s3fb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 26/28] video: fbdev: pm3fb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 27/28] video: fbdev: matroxfb: " Arvind Yadav
2017-07-20 17:51 ` [PATCH 28/28] video: fbdev: vt8623fb: " Arvind Yadav
2017-08-01 15:37 ` Bartlomiej Zolnierkiewicz [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=3297262.0f1bRl44hx@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=FlorianSchandinat@gmx.de \
--cc=adaplas@gmail.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroemme@libmpq.org \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).