From: Somnath Kotur <somnath.kotur@broadcom.com>
To: dev <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/5] bnxt patches
Date: Thu, 25 Jul 2019 10:50:45 +0530 [thread overview]
Message-ID: <CAOBf=mvP7gXz_AUsmgv_JpeSuNR-N1cATZf1fy1wCx3=4Fc3XQ@mail.gmail.com> (raw)
In-Reply-To: <20190724060158.15571-1-somnath.kotur@broadcom.com>
Ferruh,
Please ignore this set as i have sent a v2 with just 4 of the
patches below...the 1st patch in this set got pulled in to Lance's latest
patch ( (net/bnxt: use dedicated cpr for async events)
Thanks and apologies for any confusion
-Som
On Wed, Jul 24, 2019 at 11:37 AM Somnath Kotur <somnath.kotur@broadcom.com>
wrote:
> This set contains only bug fixes, that need to get into 19.08
>
> Please apply.
>
> Kalesh AP (4):
> net/bnxt: fix rxq start
> net/bnxt: fix to use chimp hwrm channel for few commands
> net/bnxt: fix endianness issue
> net/bnxt: reduce verbosity of a message
>
> Santoshkumar Karanappa Rastapur (1):
> net/bnxt: fix extended port counter statistics
>
> drivers/net/bnxt/bnxt_hwrm.c | 22 +++++++++++-----------
> drivers/net/bnxt/bnxt_ring.c | 4 ----
> drivers/net/bnxt/bnxt_rxq.c | 21 ++++++++++++++-------
> drivers/net/bnxt/bnxt_stats.c | 24 ++++++++++++++----------
> 4 files changed, 39 insertions(+), 32 deletions(-)
>
> --
> 1.8.3.1
>
>
prev parent reply other threads:[~2019-07-25 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 6:01 Somnath Kotur
2019-07-24 6:01 ` [dpdk-dev] [PATCH 1/5] net/bnxt: fix rxq start Somnath Kotur
2019-07-24 6:01 ` [dpdk-dev] [PATCH 2/5] net/bnxt: fix extended port counter statistics Somnath Kotur
2019-07-24 6:01 ` [dpdk-dev] [PATCH 3/5] net/bnxt: fix to use chimp hwrm channel for few commands Somnath Kotur
2019-07-24 6:01 ` [dpdk-dev] [PATCH 4/5] net/bnxt: fix endianness issue Somnath Kotur
2019-07-24 6:01 ` [dpdk-dev] [PATCH 5/5] net/bnxt: reduce verbosity of a message Somnath Kotur
2019-07-25 5:20 ` Somnath Kotur [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='CAOBf=mvP7gXz_AUsmgv_JpeSuNR-N1cATZf1fy1wCx3=4Fc3XQ@mail.gmail.com' \
--to=somnath.kotur@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).