From: Ajit Khaparde <ajitkhaparde@gmail.com>
To: Somnath Kotur <somnath.kotur@broadcom.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] bnxt patches
Date: Mon, 11 Jan 2021 19:41:55 -0800 [thread overview]
Message-ID: <CAD6mc5bcbJR8agb_GJAW3SKYXrSBgGZ33uZ_4vJXAbU5cvA5Xw@mail.gmail.com> (raw)
In-Reply-To: <20201224093734.13940-1-somnath.kotur@broadcom.com>
On Thu, Dec 24, 2020 at 1:46 AM Somnath Kotur
<somnath.kotur@broadcom.com> wrote:
>
> A couple of bnxt PMD fixes and an enhancement
>
> Somnath Kotur (3):
> net/bnxt: fix to init/destroy locks only once
> net/bnxt: fix error path handling of dev start op
> net/bnxt: check for chip reset in dev stop/close ops
Patchset applied to dpdk-next-net-brcm. Thanks
>
> drivers/net/bnxt/bnxt.h | 5 +
> drivers/net/bnxt/bnxt_cpr.c | 2 +
> drivers/net/bnxt/bnxt_ethdev.c | 225 +++++++++++++++++++--------------
> 3 files changed, 135 insertions(+), 97 deletions(-)
>
> --
> v1->v2: Modified patch 1/3 to return error
> 2.28.0.497.g54e85e7
>
next prev parent reply other threads:[~2021-01-12 3:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 6:31 [dpdk-dev] [PATCH " Somnath Kotur
2020-12-24 6:31 ` [dpdk-dev] [PATCH 1/3] net/bnxt: fix to init/destroy locks only once Somnath Kotur
2020-12-24 6:31 ` [dpdk-dev] [PATCH 2/3] net/bnxt: fix error path handling of dev start op Somnath Kotur
2020-12-24 6:31 ` [dpdk-dev] [PATCH 3/3] net/bnxt: check for chip reset in dev stop/close ops Somnath Kotur
2020-12-24 9:37 ` [dpdk-dev] [PATCH v2 0/3] bnxt patches Somnath Kotur
2020-12-24 9:37 ` [dpdk-dev] [PATCH 1/3] net/bnxt: fix to init/destroy locks only once Somnath Kotur
2020-12-24 9:37 ` [dpdk-dev] [PATCH 2/3] net/bnxt: fix error path handling of dev start op Somnath Kotur
2020-12-24 9:37 ` [dpdk-dev] [PATCH 3/3] net/bnxt: check for chip reset in dev stop/close ops Somnath Kotur
2021-01-12 3:41 ` Ajit Khaparde [this message]
2020-12-24 9:35 [dpdk-dev] [PATCH v2 0/3] bnxt patches Somnath Kotur
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=CAD6mc5bcbJR8agb_GJAW3SKYXrSBgGZ33uZ_4vJXAbU5cvA5Xw@mail.gmail.com \
--to=ajitkhaparde@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=somnath.kotur@broadcom.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).