From: patchwork-bot+netdevbpf@kernel.org
To: Nikhil P. Rao <nikhil.rao@amd.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, brett.creeley@amd.com,
eric.joyner@amd.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, jacob.e.keller@intel.com,
horms@kernel.org, Vamsi.Atluri@amd.com
Subject: Re: [PATCH net-next v12 0/6] pds_core: Add PLDM firmware update and host backed memory support
Date: Thu, 06 Aug 2026 01:20:23 +0000 [thread overview]
Message-ID: <178597922363.593652.16088321479084285772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260730-upstream_v8-v12-0-136cd174ee85@amd.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 30 Jul 2026 04:25:17 +0000 you wrote:
> This series adds PLDM-based firmware update support to the pds_core
> driver. PLDM (Platform Level Data Model) is a DMTF standard for firmware
> management that provides a vendor-neutral interface for firmware updates.
>
> The implementation uses the kernel's pldmfw library for package parsing
> and component matching. Users can update entire firmware packages or
> individual components via devlink flash. Component information is
> displayed via devlink info, showing firmware versions and update status
> for each component.
>
> [...]
Here is the summary with links:
- [net-next,v12,1/6] pds_core: add support for quiet devcmd failures
https://git.kernel.org/netdev/net-next/c/4b5137bfc07b
- [net-next,v12,2/6] pds_core: add support for identity version 2
https://git.kernel.org/netdev/net-next/c/e7960459d977
- [net-next,v12,3/6] pds_core: add PLDM firmware update support via devlink flash
https://git.kernel.org/netdev/net-next/c/fb918581d433
- [net-next,v12,4/6] pds_core: add PLDM component info display
https://git.kernel.org/netdev/net-next/c/5df545b3a5ee
- [net-next,v12,5/6] pds_core: add host backed memory support for firmware
https://git.kernel.org/netdev/net-next/c/b311af86b58f
- [net-next,v12,6/6] pds_core: add debugfs support for host backed memory
https://git.kernel.org/netdev/net-next/c/0b5091b64ad6
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:[~2026-08-06 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 4:25 [PATCH net-next v12 0/6] pds_core: Add PLDM firmware update and host backed memory support Nikhil P. Rao
2026-07-30 4:25 ` [PATCH net-next v12 1/6] pds_core: add support for quiet devcmd failures Nikhil P. Rao
2026-07-30 4:25 ` [PATCH net-next v12 2/6] pds_core: add support for identity version 2 Nikhil P. Rao
2026-07-30 4:25 ` [PATCH net-next v12 3/6] pds_core: add PLDM firmware update support via devlink flash Nikhil P. Rao
2026-07-30 4:25 ` [PATCH net-next v12 4/6] pds_core: add PLDM component info display Nikhil P. Rao
2026-07-30 4:25 ` [PATCH net-next v12 5/6] pds_core: add host backed memory support for firmware Nikhil P. Rao
2026-07-30 4:25 ` [PATCH net-next v12 6/6] pds_core: add debugfs support for host backed memory Nikhil P. Rao
2026-08-06 1:20 ` 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=178597922363.593652.16088321479084285772.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Vamsi.Atluri@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.joyner@amd.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikhil.rao@amd.com \
--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