From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
andrew+netdev@lunn.ch, ecree.xilinx@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/3] sfc: devlink flash for X4
Date: Tue, 25 Mar 2025 15:00:42 +0000 [thread overview]
Message-ID: <174291484274.606159.17848152999707551854.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1742493016.git.ecree.xilinx@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 20 Mar 2025 17:57:09 +0000 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/3] sfc: rip out MDIO support
https://git.kernel.org/netdev/net-next/c/c339fcdd738b
- [v2,net-next,2/3] sfc: update MCDI protocol headers
https://git.kernel.org/netdev/net-next/c/25d0c8e6f0bb
- [v2,net-next,3/3] sfc: support X4 devlink flash
https://git.kernel.org/netdev/net-next/c/5726a15499da
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-25 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 17:57 [PATCH v2 net-next 0/3] sfc: devlink flash for X4 edward.cree
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 ` patchwork-bot+netdevbpf [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=174291484274.606159.17848152999707551854.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.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 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).