DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/7] bnxt patchset with bug fixes
Date: Thu, 6 Feb 2020 10:50:14 -0800	[thread overview]
Message-ID: <CACZ4nhsRHTP4coxmr6KgyGBcCCt9Yn-PDX4L1rJMb9Cu+Wj-DQ@mail.gmail.com> (raw)
In-Reply-To: <20200206184432.34360-1-ajit.khaparde@broadcom.com>

On Thu, Feb 6, 2020 at 10:44 AM Ajit Khaparde <ajit.khaparde@broadcom.com>
wrote:

> v1->v2: fixed the commit logs.
>
Patchset applied to dpdk-next-net-brcm.


>
> Kalesh AP (5):
>   net/bnxt: fix unnecessary delay in port stop
>   net/bnxt: log firmware debug notifications
>   net/bnxt: register for debug notification event from FW
>   net/bnxt: fix to call port stop when error recovery fails
>   net/bnxt: move locally used functions to static
>
> Rahul Gupta (1):
>   net/bnxt: fix default timeout for command to get FW version
>
> Santoshkumar Karanappa Rastapur (1):
>   net/bnxt: fix buffer allocation reattempt logic
>
>  drivers/net/bnxt/bnxt.h        |  7 ++++---
>  drivers/net/bnxt/bnxt_cpr.c    |  5 +++++
>  drivers/net/bnxt/bnxt_ethdev.c | 17 ++++++++++-------
>  drivers/net/bnxt/bnxt_hwrm.c   | 29 +++++++++++++++++------------
>  drivers/net/bnxt/bnxt_hwrm.h   |  9 +++------
>  drivers/net/bnxt/bnxt_rxr.c    |  7 ++++---
>  6 files changed, 43 insertions(+), 31 deletions(-)
>
> --
> 2.21.1 (Apple Git-122.3)
>
>

      parent reply	other threads:[~2020-02-06 18:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 16:33 [dpdk-dev] [PATCH " Kalesh A P
2020-02-06 16:33 ` [dpdk-dev] [PATCH 1/7] net/bnxt: avoid an unnecessary delay in port stop Kalesh A P
2020-02-06 16:33 ` [dpdk-dev] [PATCH 2/7] net/bnxt: fix default timeout for ver_get command Kalesh A P
2020-02-06 16:33 ` [dpdk-dev] [PATCH 3/7] net/bnxt: log firmware debug notifications Kalesh A P
2020-02-06 16:33 ` [dpdk-dev] [PATCH 4/7] net/bnxt: register for debug notification async event from fw Kalesh A P
2020-02-06 16:33 ` [dpdk-dev] [PATCH 5/7] net/bnxt: fix to call port stop when error recovery fails Kalesh A P
2020-02-06 16:33 ` [dpdk-dev] [PATCH 6/7] net/bnxt: move locally used functions to static Kalesh A P
2020-02-06 16:33 ` [dpdk-dev] [PATCH 7/7] net/bnxt: fix buffer allocation reattempt logic Kalesh A P
2020-02-06 18:44 ` [dpdk-dev] [PATCH v2 0/7] bnxt patchset with bug fixes Ajit Khaparde
2020-02-06 18:44   ` [dpdk-dev] [PATCH v2 1/7] net/bnxt: fix unnecessary delay in port stop Ajit Khaparde
2020-02-06 18:44   ` [dpdk-dev] [PATCH v2 2/7] net/bnxt: fix default timeout for command to get FW version Ajit Khaparde
2020-02-06 18:44   ` [dpdk-dev] [PATCH v2 3/7] net/bnxt: log firmware debug notifications Ajit Khaparde
2020-02-06 18:44   ` [dpdk-dev] [PATCH v2 4/7] net/bnxt: register for debug notification event from FW Ajit Khaparde
2020-02-06 18:44   ` [dpdk-dev] [PATCH v2 5/7] net/bnxt: fix to call port stop when error recovery fails Ajit Khaparde
2020-02-06 18:44   ` [dpdk-dev] [PATCH v2 6/7] net/bnxt: move locally used functions to static Ajit Khaparde
2020-02-06 18:44   ` [dpdk-dev] [PATCH v2 7/7] net/bnxt: fix buffer allocation reattempt logic Ajit Khaparde
2020-02-06 18:50   ` Ajit Khaparde [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=CACZ4nhsRHTP4coxmr6KgyGBcCCt9Yn-PDX4L1rJMb9Cu+Wj-DQ@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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;
as well as URLs for NNTP newsgroup(s).