From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, gospo@broadcom.com
Subject: [PATCH net v3 0/4] bnxt_en: Misc. fixes
Date: Thu, 7 Dec 2023 16:16:54 -0800 [thread overview]
Message-ID: <20231208001658.14230-1-michael.chan@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
4 miscellaneous driver fixes covering PM resume, SKB recycling,
wrong return value check, and PTP HWTSTAMP_FILTER_ALL.
v3: Fix Fixes tag in patch 1 and improve patch 3.
v2: Fix SOB tags in patch 1 and 3.
Kalesh AP (1):
bnxt_en: Fix wrong return value check in bnxt_close_nic()
Michael Chan (1):
bnxt_en: Fix HWTSTAMP_FILTER_ALL packet timestamp logic
Somnath Kotur (1):
bnxt_en: Clear resource reservation during resume
Sreekanth Reddy (1):
bnxt_en: Fix skb recycling logic in bnxt_deliver_skb()
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 38 ++++++++++++++-----
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 10 ++++-
.../net/ethernet/broadcom/bnxt/bnxt_devlink.c | 11 +-----
.../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 19 ++--------
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c | 5 +--
5 files changed, 44 insertions(+), 39 deletions(-)
--
2.30.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
next reply other threads:[~2023-12-08 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 0:16 Michael Chan [this message]
2023-12-08 0:16 ` [PATCH net v3 1/4] bnxt_en: Clear resource reservation during resume Michael Chan
2023-12-08 0:16 ` [PATCH net v3 2/4] bnxt_en: Fix skb recycling logic in bnxt_deliver_skb() Michael Chan
2023-12-08 0:16 ` [PATCH net v3 3/4] bnxt_en: Fix wrong return value check in bnxt_close_nic() Michael Chan
2023-12-08 0:16 ` [PATCH net v3 4/4] bnxt_en: Fix HWTSTAMP_FILTER_ALL packet timestamp logic Michael Chan
2023-12-09 1:40 ` [PATCH net v3 0/4] bnxt_en: Misc. fixes patchwork-bot+netdevbpf
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=20231208001658.14230-1-michael.chan@broadcom.com \
--to=michael.chan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).