From: Doug Ledford <dledford@redhat.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
aditr@vmware.com, pv-drivers@vmware.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com
Subject: Re: [PATCH 0/3] constify infiniband pci_device_id.
Date: Fri, 18 Aug 2017 12:03:12 -0400 [thread overview]
Message-ID: <1503072192.2598.16.camel@redhat.com> (raw)
In-Reply-To: <1500186646-28815-1-git-send-email-arvind.yadav.cs@gmail.com>
On Sun, 2017-07-16 at 12:00 +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.
>
> Arvind Yadav (3):
> [PATCH 1/3] infiniband: mthca: constify pci_device_id.
> [PATCH 2/3] infiniband: nes: constify pci_device_id.
> [PATCH 3/3] infiniband: pvrdma: constify pci_device_id.
>
> drivers/infiniband/hw/mthca/mthca_main.c | 2 +-
> drivers/infiniband/hw/nes/nes.c | 2 +-
> drivers/infiniband/hw/vmw_pvrdma/pvrdma_main.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
Thanks, series applied.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
prev parent reply other threads:[~2017-08-18 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 6:30 [PATCH 0/3] constify infiniband pci_device_id Arvind Yadav
2017-07-16 6:30 ` [PATCH 1/3] infiniband: mthca: constify pci_device_id Arvind Yadav
2017-07-16 6:30 ` [PATCH 2/3] infiniband: nes: " Arvind Yadav
2017-07-16 6:30 ` [PATCH 3/3] infiniband: pvrdma: " Arvind Yadav
2017-08-18 16:03 ` Doug Ledford [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=1503072192.2598.16.camel@redhat.com \
--to=dledford@redhat.com \
--cc=aditr@vmware.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=sean.hefty@intel.com \
/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