From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] bnxt bug fixes
Date: Wed, 19 Feb 2020 22:23:04 -0800 [thread overview]
Message-ID: <CACZ4nhuCDfQ4AUvvmKcahMDfBYYuvdfUR58b+74fS_68sX3aZw@mail.gmail.com> (raw)
In-Reply-To: <20200220041214.18053-1-kalesh-anakkur.purayil@broadcom.com>
On Wed, Feb 19, 2020 at 7:55 PM Kalesh A P <
kalesh-anakkur.purayil@broadcom.com> wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> These are couple of bnxt PMD bug fixes. Please apply.
>
Patches applied to dpdk-next-net-brcm.
>
> Kalesh AP (2):
> net/bnxt: fix segmentation fault handling async events on port stop
> net/bnxt: fix race when port is stopped and async events are received
>
> drivers/net/bnxt/bnxt_cpr.c | 6 ++++++
> drivers/net/bnxt/bnxt_hwrm.c | 12 +++++++++---
> 2 files changed, 15 insertions(+), 3 deletions(-)
>
> --
> 2.10.1
>
>
next prev parent reply other threads:[~2020-02-20 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 4:12 Kalesh A P
2020-02-20 4:12 ` [dpdk-dev] [PATCH 1/2] net/bnxt: fix segmentation fault handling async events on port stop Kalesh A P
2020-02-20 4:12 ` [dpdk-dev] [PATCH 2/2] net/bnxt: fix race when port is stopped and async events are received Kalesh A P
2020-02-20 6:23 ` Ajit Khaparde [this message]
2020-04-23 15:02 [dpdk-dev] [PATCH 0/2] bnxt bug fixes Kalesh A P
2020-04-23 22:50 ` Ajit Khaparde
2020-05-06 6:27 Kalesh A P
2020-05-07 3:22 ` Ajit Khaparde
2020-05-22 17:32 Kalesh A P
2021-03-10 7:50 Kalesh A P
2021-03-11 23:58 ` Ajit Khaparde
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=CACZ4nhuCDfQ4AUvvmKcahMDfBYYuvdfUR58b+74fS_68sX3aZw@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kalesh-anakkur.purayil@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).