patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 18.11 0/3] bnxt patches for 18.11
Date: Fri, 30 Oct 2020 13:13:02 +0000	[thread overview]
Message-ID: <e028c69b-af34-9125-b8c1-90a485fdcbfd@redhat.com> (raw)
In-Reply-To: <20201016092047.30846-1-kalesh-anakkur.purayil@broadcom.com>

On 16/10/2020 10:20, Kalesh A P wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> 
> Hi Kevin,
> 
> I have back ported few of the conflicting patches to 18.11 stable.
> Other patches in the list, you can ignore and those are not needed.
> 
> Kalesh AP (1):
>   net/bnxt: fix flow error on filter creation
> 
> Rahul Gupta (2):
>   net/bnxt: fix for memleak during queue restart
>   net/bnxt: fix to advance producer index
> 
>  drivers/net/bnxt/bnxt_flow.c | 12 ++++++++++++
>  drivers/net/bnxt/bnxt_hwrm.c | 12 ------------
>  drivers/net/bnxt/bnxt_rxr.c  | 36 +++++++++++++++++++++---------------
>  3 files changed, 33 insertions(+), 27 deletions(-)
> 

Applied and removed other bnxt commits from failed list, thanks.


      parent reply	other threads:[~2020-10-30 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16  9:20 Kalesh A P
2020-10-16  9:20 ` [dpdk-stable] [PATCH 18.11 1/3] net/bnxt: fix for memleak during queue restart Kalesh A P
2020-10-16  9:20 ` [dpdk-stable] [PATCH 18.11 2/3] net/bnxt: fix to advance producer index Kalesh A P
2020-10-16  9:20 ` [dpdk-stable] [PATCH 18.11 3/3] net/bnxt: fix flow error on filter creation Kalesh A P
2020-10-16 12:26 ` [dpdk-stable] [PATCH 18.11 0/3] bnxt patches for 18.11 Kevin Traynor
2020-10-30 13:13 ` Kevin Traynor [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=e028c69b-af34-9125-b8c1-90a485fdcbfd@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=kalesh-anakkur.purayil@broadcom.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).