From: <edward.cree@amd.com>
To: <linux-net-drivers@amd.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <edumazet@google.com>, <pabeni@redhat.com>,
<horms@kernel.org>, <andrew+netdev@lunn.ch>
Cc: Edward Cree <ecree.xilinx@gmail.com>, <netdev@vger.kernel.org>
Subject: [PATCH v2 net-next 0/3] sfc: devlink flash for X4
Date: Thu, 20 Mar 2025 17:57:09 +0000 [thread overview]
Message-ID: <cover.1742493016.git.ecree.xilinx@gmail.com> (raw)
From: Edward Cree <ecree.xilinx@gmail.com>
Updates to support devlink flash on X4 NICs.
Patch #2 is needed for NVRAM_PARTITION_TYPE_AUTO, and patch #1 is
needed because the latest MCDI headers from firmware no longer
include MDIO read/write commands.
Changed in version 2:
* patch #3: fixed lock leak and removed resulting unused label
v1 posting:
Link: https://lore.kernel.org/netdev/cover.1742223233.git.ecree.xilinx@gmail.com/
Edward Cree (3):
sfc: rip out MDIO support
sfc: update MCDI protocol headers
sfc: support X4 devlink flash
drivers/net/ethernet/sfc/ef10.c | 1 +
drivers/net/ethernet/sfc/ef100_netdev.c | 1 -
drivers/net/ethernet/sfc/efx.c | 24 -
drivers/net/ethernet/sfc/efx_reflash.c | 52 +-
drivers/net/ethernet/sfc/mcdi_pcol.h | 20158 +++++++-----------
drivers/net/ethernet/sfc/mcdi_port.c | 59 +-
drivers/net/ethernet/sfc/mcdi_port_common.c | 11 -
drivers/net/ethernet/sfc/net_driver.h | 9 +-
8 files changed, 8222 insertions(+), 12093 deletions(-)
next reply other threads:[~2025-03-20 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 17:57 edward.cree [this message]
2025-03-20 17:57 ` [PATCH v2 net-next 1/3] sfc: rip out MDIO support edward.cree
2025-03-20 17:57 ` [PATCH v2 net-next 2/3] sfc: update MCDI protocol headers edward.cree
2025-03-20 17:57 ` [PATCH v2 net-next 3/3] sfc: support X4 devlink flash edward.cree
2025-03-25 15:00 ` [PATCH v2 net-next 0/3] sfc: devlink flash for X4 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=cover.1742493016.git.ecree.xilinx@gmail.com \
--to=edward.cree@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--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.