From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, corbet@lwn.net, Prathosh.Satish@microchip.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
mschmidt@redhat.com, poros@redhat.com,
przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next v6 0/5] dpll: zl3073x: Add support for devlink flash
Date: Mon, 15 Sep 2025 15:30:13 +0000 [thread overview]
Message-ID: <175795021328.29952.16558907395592843610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250909091532.11790-1-ivecera@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 9 Sep 2025 11:15:27 +0200 you wrote:
> Add functionality for accessing device hardware registers, loading
> firmware bundles, and accessing the device's internal flash memory,
> and use it to implement the devlink flash functionality.
>
> Patch breakdown:
> Patch1: helpers to access hardware registers
> Patch2: low level functions to access flash memory
> Patch3: support to load firmware bundles
> Patch4: refactoring device initialization and helper functions
> for stopping and resuming device normal operation
> Patch5: devlink .flash_update callback implementation
>
> [...]
Here is the summary with links:
- [net-next,v6,1/5] dpll: zl3073x: Add functions to access hardware registers
https://git.kernel.org/netdev/net-next/c/259ede9da4ec
- [net-next,v6,2/5] dpll: zl3073x: Add low-level flash functions
https://git.kernel.org/netdev/net-next/c/3639bd087679
- [net-next,v6,3/5] dpll: zl3073x: Add firmware loading functionality
https://git.kernel.org/netdev/net-next/c/ca017409da69
- [net-next,v6,4/5] dpll: zl3073x: Refactor DPLL initialization
https://git.kernel.org/netdev/net-next/c/ebb1031c5137
- [net-next,v6,5/5] dpll: zl3073x: Implement devlink flash callback
https://git.kernel.org/netdev/net-next/c/a1e891fe4ae8
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-09-15 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 9:15 [PATCH net-next v6 0/5] dpll: zl3073x: Add support for devlink flash Ivan Vecera
2025-09-09 9:15 ` [PATCH net-next v6 1/5] dpll: zl3073x: Add functions to access hardware registers Ivan Vecera
2025-09-09 9:15 ` [PATCH net-next v6 2/5] dpll: zl3073x: Add low-level flash functions Ivan Vecera
2025-09-09 9:15 ` [PATCH net-next v6 3/5] dpll: zl3073x: Add firmware loading functionality Ivan Vecera
2025-09-14 21:45 ` Jakub Kicinski
2025-09-15 8:18 ` Ivan Vecera
2025-09-15 15:08 ` Jakub Kicinski
2025-09-09 9:15 ` [PATCH net-next v6 4/5] dpll: zl3073x: Refactor DPLL initialization Ivan Vecera
2025-09-09 9:15 ` [PATCH net-next v6 5/5] dpll: zl3073x: Implement devlink flash callback Ivan Vecera
2025-09-15 15:30 ` 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=175795021328.29952.16558907395592843610.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=przemyslaw.kitszel@intel.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.