From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/qat: make PCI device id struct const
Date: Fri, 27 Jan 2017 08:37:49 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476D0521@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <6a3da59e-6fd5-6880-ecb9-57a7e1faddc6@nxp.com>
> -----Original Message-----
> From: Shreyansh Jain [mailto:shreyansh.jain@nxp.com]
> Sent: Friday, January 27, 2017 7:11 AM
> To: Yigit, Ferruh
> Cc: dev@dpdk.org; Thomas Monjalon; De Lara Guarch, Pablo
> Subject: Re: [PATCH] crypto/qat: make PCI device id struct const
>
> On Thursday 26 January 2017 07:37 PM, Ferruh Yigit wrote:
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> > ---
> > drivers/crypto/qat/rte_qat_cryptodev.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/crypto/qat/rte_qat_cryptodev.c
> b/drivers/crypto/qat/rte_qat_cryptodev.c
> > index 9594067..a492dc0 100644
> > --- a/drivers/crypto/qat/rte_qat_cryptodev.c
> > +++ b/drivers/crypto/qat/rte_qat_cryptodev.c
> > @@ -67,7 +67,7 @@ static struct rte_cryptodev_ops crypto_qat_ops = {
> > * The set of PCI devices this driver supports
> > */
> >
> > -static struct rte_pci_id pci_id_qat_map[] = {
> > +static const struct rte_pci_id pci_id_qat_map[] = {
> > {
> > RTE_PCI_DEVICE(0x8086, 0x0443),
> > },
> >
>
> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-01-27 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 14:07 Ferruh Yigit
2017-01-27 7:10 ` Shreyansh Jain
2017-01-27 8:37 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D897476D0521@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=thomas.monjalon@6wind.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;
as well as URLs for NNTP newsgroup(s).