public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, Prathosh.Satish@microchip.com,
	vadim.fedorenko@linux.dev, arkadiusz.kubalewski@intel.com,
	jiri@resnulli.us, kuba@kernel.org, przemyslaw.kitszel@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] dpll: zl3073x: Increase maximum size of flash utility
Date: Fri, 10 Oct 2025 08:40:09 +0000	[thread overview]
Message-ID: <176008560900.506662.10655355854851923523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251008141418.841053-1-ivecera@redhat.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Wed,  8 Oct 2025 16:14:18 +0200 you wrote:
> Newer firmware bundles contain a flash utility whose size exceeds
> the currently allowed limit. Increase the maximum allowed size
> to accommodate the newer utility version.
> 
> Without this patch:
>  # devlink dev flash i2c/1-0070 file fw_nosplit_v3.hex
>  Failed to load firmware
>  Flashing failed
>  Error: zl3073x: FW load failed: [utility] component is too big (11000 bytes)
> 
> [...]

Here is the summary with links:
  - [net] dpll: zl3073x: Increase maximum size of flash utility
    https://git.kernel.org/netdev/net/c/f3426ac54c42

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-10-10  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08 14:14 [PATCH net] dpll: zl3073x: Increase maximum size of flash utility Ivan Vecera
2025-10-08 15:19 ` Vadim Fedorenko
2025-10-10  8:40 ` 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=176008560900.506662.10655355854851923523.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Prathosh.Satish@microchip.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=vadim.fedorenko@linux.dev \
    /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