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 0/2] bnxt_en: Bug fixes
Date: Sun, 16 Apr 2023 23:58:17 -0700 [thread overview]
Message-ID: <20230417065819.122055-1-michael.chan@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
This small series contains 2 fixes. The first one fixes the PTP
initialization logic on older chips to avoid logging a warning. The
second one fixes a potenial NULL pointer dereference in the driver's
aux bus unload path.
Kalesh AP (1):
bnxt_en: Fix a possible NULL pointer dereference in unload path
Michael Chan (1):
bnxt_en: Do not initialize PTP on older P3/P4 chips
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 2 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 19 ++++++++++---------
2 files changed, 11 insertions(+), 10 deletions(-)
--
2.18.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
next reply other threads:[~2023-04-17 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 6:58 Michael Chan [this message]
2023-04-17 6:58 ` [PATCH net 1/2] bnxt_en: Do not initialize PTP on older P3/P4 chips Michael Chan
2023-04-17 6:58 ` [PATCH net 2/2] bnxt_en: Fix a possible NULL pointer dereference in unload path Michael Chan
2023-04-18 10:40 ` [PATCH net 0/2] bnxt_en: Bug fixes patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2021-01-11 9:26 Michael Chan
2021-01-13 4:10 ` patchwork-bot+netdevbpf
2020-12-27 19:18 Michael Chan
2020-12-28 22:20 ` 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=20230417065819.122055-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.