Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, vadim.fedorenko@linux.dev,
	arkadiusz.kubalewski@intel.com, jiri@resnulli.us,
	Prathosh.Satish@microchip.com, kuba@kernel.org, poros@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/3] dpll: zl3073x: various fixes
Date: Thu, 28 May 2026 12:10:10 +0000	[thread overview]
Message-ID: <177997021014.896679.13961850181494298795.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260526074525.1451008-1-ivecera@redhat.com>

Hello:

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

On Tue, 26 May 2026 09:45:22 +0200 you wrote:
> Three fixes for the zl3073x DPLL driver.
> 
> Patch 1 exports __dpll_device_change_ntf() for use by drivers that
> need to send device change notifications from within callbacks
> already running under dpll_lock.
> 
> Patch 2 replaces the change_work workqueue mechanism with direct
> calls to __dpll_device_change_ntf(), eliminating a race condition
> where the work handler could dereference a freed dpll_dev pointer
> during device teardown.
> 
> [...]

Here is the summary with links:
  - [net,1/3] dpll: export __dpll_device_change_ntf() for use under dpll_lock
    https://git.kernel.org/netdev/net/c/20040b2a3cb9
  - [net,2/3] dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work
    https://git.kernel.org/netdev/net/c/d733f519f644
  - [net,3/3] dpll: zl3073x: make frequency monitor a per-device attribute
    https://git.kernel.org/netdev/net/c/c1224569cef0

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



      parent reply	other threads:[~2026-05-28 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  7:45 [PATCH net 0/3] dpll: zl3073x: various fixes Ivan Vecera
2026-05-26  7:45 ` [PATCH net 1/3] dpll: export __dpll_device_change_ntf() for use under dpll_lock Ivan Vecera
2026-05-26 13:29   ` Jiri Pirko
2026-05-26  7:45 ` [PATCH net 2/3] dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work Ivan Vecera
2026-05-27  7:51   ` Ivan Vecera
2026-05-27 23:29     ` Jakub Kicinski
2026-05-26  7:45 ` [PATCH net 3/3] dpll: zl3073x: make frequency monitor a per-device attribute Ivan Vecera
2026-05-28 12:10 ` 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=177997021014.896679.13961850181494298795.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=poros@redhat.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