The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Pirko <jiri@resnulli.us>, <netdev@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Prathosh Satish <Prathosh.Satish@microchip.com>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Michal Schmidt <mschmidt@redhat.com>,
	"Petr Oros" <poros@redhat.com>
Subject: Re: [PATCH net-next v4 0/5] dpll: zl3073x: Add support for devlink flash
Date: Fri, 5 Sep 2025 15:07:55 +0200	[thread overview]
Message-ID: <b5be0b7d-35e4-43ca-85f6-fa17c139edba@intel.com> (raw)
In-Reply-To: <20250903100900.8470-1-ivecera@redhat.com>

On 9/3/25 12:08, Ivan Vecera 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
> 
> Changes:
> v4:
> * fixed issues reported by Jakub (see patches' changelogs)
> v3:
> * fixed issues reported by Przemek (see patches' changelogs)

in general you should carry tags added in previous revisions,
especially if there were no big/opposing/controversial changes
anyway, for the series:
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>

> v2:
> * fixed several warnings found by patchwork bot
> * added includes into new .c files
> * fixed typos
> * fixed uninitialized variable
> 
> Ivan Vecera (5):
>    dpll: zl3073x: Add functions to access hardware registers
>    dpll: zl3073x: Add low-level flash functions
>    dpll: zl3073x: Add firmware loading functionality

overflow prevention added here looks good

>    dpll: zl3073x: Refactor DPLL initialization
>    dpll: zl3073x: Implement devlink flash callback
> 
>   Documentation/networking/devlink/zl3073x.rst |  14 +
>   drivers/dpll/zl3073x/Makefile                |   2 +-
>   drivers/dpll/zl3073x/core.c                  | 362 +++++++---
>   drivers/dpll/zl3073x/core.h                  |  33 +
>   drivers/dpll/zl3073x/devlink.c               | 154 ++++-
>   drivers/dpll/zl3073x/devlink.h               |   3 +
>   drivers/dpll/zl3073x/flash.c                 | 674 +++++++++++++++++++
>   drivers/dpll/zl3073x/flash.h                 |  29 +
>   drivers/dpll/zl3073x/fw.c                    | 419 ++++++++++++
>   drivers/dpll/zl3073x/fw.h                    |  52 ++
>   drivers/dpll/zl3073x/regs.h                  |  51 ++
>   11 files changed, 1702 insertions(+), 91 deletions(-)
>   create mode 100644 drivers/dpll/zl3073x/flash.c
>   create mode 100644 drivers/dpll/zl3073x/flash.h
>   create mode 100644 drivers/dpll/zl3073x/fw.c
>   create mode 100644 drivers/dpll/zl3073x/fw.h
> 


      parent reply	other threads:[~2025-09-05 13:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 10:08 [PATCH net-next v4 0/5] dpll: zl3073x: Add support for devlink flash Ivan Vecera
2025-09-03 10:08 ` [PATCH net-next v4 1/5] dpll: zl3073x: Add functions to access hardware registers Ivan Vecera
2025-09-03 10:08 ` [PATCH net-next v4 2/5] dpll: zl3073x: Add low-level flash functions Ivan Vecera
2025-09-06  2:19   ` Jakub Kicinski
2025-09-06  6:57     ` Ivan Vecera
2025-09-03 10:08 ` [PATCH net-next v4 3/5] dpll: zl3073x: Add firmware loading functionality Ivan Vecera
2025-09-03 10:08 ` [PATCH net-next v4 4/5] dpll: zl3073x: Refactor DPLL initialization Ivan Vecera
2025-09-03 10:09 ` [PATCH net-next v4 5/5] dpll: zl3073x: Implement devlink flash callback Ivan Vecera
2025-09-05 13:07 ` Przemek Kitszel [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=b5be0b7d-35e4-43ca-85f6-fa17c139edba@intel.com \
    --to=przemyslaw.kitszel@intel.com \
    --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 \
    /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