From: Jiri Pirko <jiri@resnulli.us>
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Jakub Kicinski <kuba@kernel.org>, Petr Oros <poros@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 1/3] dpll: export __dpll_device_change_ntf() for use under dpll_lock
Date: Tue, 26 May 2026 15:29:15 +0200 [thread overview]
Message-ID: <ahWgJS65myAHz8QQ@FV6GYCPJ69> (raw)
In-Reply-To: <20260526074525.1451008-2-ivecera@redhat.com>
Tue, May 26, 2026 at 09:45:23AM +0200, ivecera@redhat.com wrote:
>Export __dpll_device_change_ntf() so that drivers can send device
>change notifications from within device callbacks, which are already
>called under dpll_lock. Using dpll_device_change_ntf() in that
>context would deadlock.
>
>Add lockdep_assert_held() to catch misuse without the lock held.
>
>Signed-off-by: Ivan Vecera <ivecera@redhat.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2026-05-26 13:29 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 [this message]
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 ` [PATCH net 0/3] dpll: zl3073x: various fixes patchwork-bot+netdevbpf
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=ahWgJS65myAHz8QQ@FV6GYCPJ69 \
--to=jiri@resnulli.us \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=ivecera@redhat.com \
--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 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.