patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 18.11 0/5] Backporting bnxt patches to 18.11
Date: Wed, 2 Dec 2020 21:57:12 +0530	[thread overview]
Message-ID: <CAH-L+nOqTwJE=AT2xSSbyM2-Q_1NAGAxfYmLPhhhx3UbjTF=CA@mail.gmail.com> (raw)
In-Reply-To: <f952807b-3956-ada1-98b8-d0297fa74a68@redhat.com>

Hi Kevin,

On Wed, 2 Dec 2020 at 8:20 PM, Kevin Traynor <ktraynor@redhat.com> wrote:

> On 01/12/2020 03:39, Kalesh A P wrote:
> > From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> >
> > Hi Kevin,
> >
>
> Hi Kalesh,
>
> > I have back ported conflicting patches to 18.11 LTS.
> >
>
> Thanks for sending, they are running^Wcrawling in travis atm.
>
> Are these the only bnxt fixes needed? the others in the list are:
>
> $ grep bnxt failed-list-running
> c92f053d4  Kalesh AP        net/bnxt: fix L2 filter allocation
> 99ad2abc0  Kalesh AP        net/bnxt: fix speed setting on certain adapters

[Kalesh] these 2 are not needed for 18.11

>
> 4b029f02d  Somnath Kotur    net/bnxt: fix checking VNIC in shutdown path

[Kalesh] oops, my bad. I missed this one in the list. I need to check

>
> ef10add37  Venkat Duvvuru   net/bnxt: fix PF support in SR-IOV mode

[Kalesh] this one is not needed for 18.11

>
> 97c327178  Somnath Kotur    net/bnxt: fix queue release
> 0b42b92ae  Ferruh Yigit     net/bnxt: fix xstats by id
> 1ef8c6290  Stephen Hemminger net/bnxt: remove useless prefetches

[Kalesh] again my bad, missed these 3 and I need to check

>
>
> Kevin.
>
> > Please apply.
> >
> > Kalesh AP (5):
> >   net/bnxt: fix structure variable initialization
> >   net/bnxt: fix UDP tunnel port removal
> >   net/bnxt: fix boolean operator usage
> >   net/bnxt: fix drop enable in get Rx queue info
> >   net/bnxt: increase size of Rx CQ
> >
> >  drivers/net/bnxt/bnxt_ethdev.c | 15 +++------------
> >  drivers/net/bnxt/bnxt_hwrm.c   | 15 +++++++++++++--
> >  drivers/net/bnxt/bnxt_ring.h   |  2 +-
> >  drivers/net/bnxt/bnxt_rxq.c    |  5 +++++
> >  drivers/net/bnxt/bnxt_rxq.h    |  4 ++++
> >  drivers/net/bnxt/bnxt_rxr.c    |  3 +++
> >  drivers/net/bnxt/bnxt_txr.c    |  2 ++
> >  7 files changed, 31 insertions(+), 15 deletions(-)
> >
>
> --
Regards,
Kalesh A P

  reply	other threads:[~2020-12-02 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01  3:39 Kalesh A P
2020-12-01  3:39 ` [dpdk-stable] [PATCH 18.11 1/5] net/bnxt: fix structure variable initialization Kalesh A P
2020-12-01  3:39 ` [dpdk-stable] [PATCH 18.11 2/5] net/bnxt: fix UDP tunnel port removal Kalesh A P
2020-12-01  3:39 ` [dpdk-stable] [PATCH 18.11 3/5] net/bnxt: fix boolean operator usage Kalesh A P
2020-12-01  3:39 ` [dpdk-stable] [PATCH 18.11 4/5] net/bnxt: fix drop enable in get Rx queue info Kalesh A P
2020-12-01  3:39 ` [dpdk-stable] [PATCH 18.11 5/5] net/bnxt: increase size of Rx CQ Kalesh A P
2020-12-02 14:50 ` [dpdk-stable] [PATCH 18.11 0/5] Backporting bnxt patches to 18.11 Kevin Traynor
2020-12-02 16:27   ` Kalesh Anakkur Purayil [this message]
2020-12-03  4:48     ` Somnath Kotur
2020-12-03 16:39 ` Kevin Traynor

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='CAH-L+nOqTwJE=AT2xSSbyM2-Q_1NAGAxfYmLPhhhx3UbjTF=CA@mail.gmail.com' \
    --to=kalesh-anakkur.purayil@broadcom.com \
    --cc=ktraynor@redhat.com \
    --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).