From: Somnath Kotur <somnath.kotur@broadcom.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: [dpdk-dev] [PATCH v2 0/4] bnxt patches
Date: Thu, 25 Jul 2019 10:29:45 +0530 [thread overview]
Message-ID: <20190725045949.27407-1-somnath.kotur@broadcom.com> (raw)
This set contains bug fixes for commits that made it into
19.08, so it's imperative that these go into 19.08 as well
Please apply
Kalesh AP (3):
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_stats.c | 24 ++++++++++++++----------
2 files changed, 25 insertions(+), 21 deletions(-)
--
v2: Removed a commit from the set as it got in as part of
Lance's commit (net/bnxt: use dedicated cpr for async events)
1.8.3.1
next reply other threads:[~2019-07-25 5:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 4:59 Somnath Kotur [this message]
2019-07-25 4:59 ` [dpdk-dev] [PATCH 1/4] net/bnxt: fix extended port counter statistics Somnath Kotur
2019-07-25 7:21 ` David Marchand
2019-07-25 7:40 ` Somnath Kotur
2019-07-25 7:54 ` Santoshkumar Karanappa Rastapur
2019-07-25 7:57 ` David Marchand
2019-07-25 7:37 ` Somnath Kotur
2019-07-25 4:59 ` [dpdk-dev] [PATCH 2/4] net/bnxt: fix to use chimp hwrm channel for few commands Somnath Kotur
2019-07-25 4:59 ` [dpdk-dev] [PATCH 3/4] net/bnxt: fix endianness issue Somnath Kotur
2019-07-25 4:59 ` [dpdk-dev] [PATCH 4/4] net/bnxt: reduce verbosity of a message Somnath Kotur
2019-07-25 15:57 ` [dpdk-dev] [PATCH v2 0/4] bnxt patches Ferruh Yigit
2020-07-29 21:23 [dpdk-dev] [PATCH " Ajit Khaparde
2020-07-31 17:22 ` [dpdk-dev] [PATCH v2 " 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=20190725045949.27407-1-somnath.kotur@broadcom.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).