patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
To: Luca Boccassi <bluca@debian.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 0/1] Request to backport 1f4a84672ecbd to 16.11
Date: Wed, 13 Dec 2017 05:56:03 -0800	[thread overview]
Message-ID: <-3582351540096258118@unknownmsgid> (raw)
In-Reply-To: <1513169892.15861.29.camel@debian.org>

On Dec 13, 2017, at 04:58, Luca Boccassi <bluca@debian.org> wrote:

On Tue, 2017-12-12 at 11:38 -0800, Ajit Khaparde wrote:

Hi,

This is probably an unusual backport request.

But to faciltate a vendor, could you please coonsider applying

commit id 1f4a84672ecbd to 16.11 LTE release?


Please let me know.


Thanks

Ajit


Ajit Khaparde (1):

  net/bnxt: support new PCI IDs


 drivers/net/bnxt/bnxt_ethdev.c | 30 ++++++++++++++++++++++++++++++

 1 file changed, 30 insertions(+)



Hi,

This would be fine, but 2 questions first:

1) Are those PCI IDs merged in the mainline?

Yes. The commit id is from the mainline tree.

2) Have those devices, or at least a subset, been tested with 16.11.x?

Yes. We have been testing DPDK on these devices.

Thanks
Ajit


-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2017-12-13 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 19:38 Ajit Khaparde
2017-12-12 19:39 ` [dpdk-stable] [PATCH 1/1] net/bnxt: support new PCI IDs Ajit Khaparde
2017-12-13 15:19   ` Luca Boccassi
2017-12-13 12:58 ` [dpdk-stable] [PATCH 0/1] Request to backport 1f4a84672ecbd to 16.11 Luca Boccassi
2017-12-13 13:56   ` Ajit Kumar Khaparde [this message]
2017-12-13 15:19     ` Luca Boccassi

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=-3582351540096258118@unknownmsgid \
    --to=ajit.khaparde@broadcom.com \
    --cc=bluca@debian.org \
    --cc=stable@dpdk.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).