From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: Eliav Farber <farbere@amazon.com>,
rafael@kernel.org, tony.luck@intel.com, bp@alien8.de,
guohanjun@huawei.com, mchehab@kernel.org,
xueshuai@linux.alibaba.com, lenb@kernel.org,
laurent.pinchart@ideasonboard.com, brgl@kernel.org,
orsonzhai@gmail.com, baolin.wang@linux.alibaba.com,
zhang.lyra@gmail.com, jic23@kernel.org, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, dmitry.torokhov@gmail.com,
hansg@kernel.org, ilpo.jarvinen@linux.intel.com, W_Armin@gmx.de,
fabio.m.de.francesco@linux.intel.com, kaihengf@nvidia.com,
ankita@nvidia.com, leitao@debian.org, pedro.pbg@usp.br,
paulmck@kernel.org, frederic@kernel.org, kees@kernel.org,
saket.dumbre@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-iio@vger.kernel.org,
linux-input@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
acpica-devel@lists.linux.dev
Subject: Re: [PATCH v5 01/13] notifier: add device-managed registration APIs
Date: Tue, 18 Aug 2026 10:26:52 +0200 [thread overview]
Message-ID: <aoQWOsPeyU9o3Ahn@monoceros> (raw)
In-Reply-To: <CAD++jLk+MMH=-ifdSs=Vm4G9RO5-yVs8NLUb4AE1wYH5FQrmjg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
Hello Linus,
On Mon, Aug 17, 2026 at 02:10:13PM +0200, Linus Walleij wrote:
> On Sun, Aug 16, 2026 at 9:04 AM Uwe Kleine-König <ukleinek@kernel.org> wrote:
>
> > I suggested to add "Must be called in process context." to the kdoc for
> > devm_atomic_notifier_chain_register() as this is a relevant difference
> > to atomic_notifier_chain_register() and create an immutable branch for
> > it as a base for subsystems to apply their follow-up patches. I'd wait
> > till Wednesday for concerns and review tags to tickle in.
>
> I think this is a good approach, but we are in the merge window,
> don't you wanna wait for v7.3-rc1 and create the immutable branch
> based on that?
My thought was to base on v7.2, and then consider the topic done for me.
> (But Bartosz will be the one pulling the immutable branch...)
It shouldn't make a difference for him if the branch's base is v7.2 or
v7.3-rc1, still more given that there are no changes staged in next to
the affected files (`git log v7.2..next/master --
include/linux/notifier.h kernel/notifier.c`).
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-08-18 8:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 6:05 [PATCH v5 00/13] notifier: add device-managed registration APIs and convert drivers Eliav Farber
2026-08-16 6:06 ` [PATCH v5 01/13] notifier: add device-managed registration APIs Eliav Farber
2026-08-16 7:04 ` Uwe Kleine-König
2026-08-17 12:10 ` Linus Walleij
2026-08-18 8:26 ` Uwe Kleine-König [this message]
2026-08-16 6:06 ` [PATCH v5 02/13] pwm: iqs620a: use devm_blocking_notifier_chain_register() Eliav Farber
2026-08-22 6:40 ` Uwe Kleine-König
2026-08-16 6:06 ` [PATCH v5 03/13] iio: light: iqs621-als: " Eliav Farber
2026-08-16 6:06 ` [PATCH v5 04/13] iio: position: iqs624: " Eliav Farber
2026-08-16 6:06 ` [PATCH v5 05/13] gpio: adp5585: " Eliav Farber
2026-08-17 12:12 ` Linus Walleij
2026-08-16 6:06 ` [PATCH v5 06/13] platform/x86: bitland-mifs-wmi: " Eliav Farber
2026-08-16 6:06 ` [PATCH v5 07/13] Input: adp5585: " Eliav Farber
2026-08-16 6:06 ` [PATCH v5 08/13] ACPI: APEI: GHES: remove unused ghes_{,un}register_vendor_record_notifier() Eliav Farber
2026-08-16 6:06 ` [PATCH v5 09/13] ACPI: APEI: GHES: use devm_blocking_notifier_chain_register() Eliav Farber
2026-08-16 6:06 ` [PATCH v5 10/13] platform/x86: uniwill-wmi: " Eliav Farber
2026-08-16 6:06 ` [PATCH v5 11/13] gpio: eic-sprd: use devm_atomic_notifier_chain_register() Eliav Farber
2026-08-17 12:12 ` Linus Walleij
2026-08-16 6:06 ` [PATCH v5 12/13] gpio: gpiolib-kunit: use devm_blocking_notifier_chain_register() Eliav Farber
2026-08-17 12:12 ` Linus Walleij
2026-08-16 6:06 ` [PATCH v5 13/13] reboot: " Eliav Farber
2026-08-21 14:07 ` [GIT PULL] Base commit for devm_{atomic,blocking}_notifier_chain_register() Uwe Kleine-König
2026-08-22 6:31 ` Uwe Kleine-König
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=aoQWOsPeyU9o3Ahn@monoceros \
--to=ukleinek@kernel.org \
--cc=W_Armin@gmx.de \
--cc=acpica-devel@lists.linux.dev \
--cc=andy@kernel.org \
--cc=ankita@nvidia.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=brgl@kernel.org \
--cc=dlechner@baylibre.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fabio.m.de.francesco@linux.intel.com \
--cc=farbere@amazon.com \
--cc=frederic@kernel.org \
--cc=guohanjun@huawei.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jic23@kernel.org \
--cc=kaihengf@nvidia.com \
--cc=kees@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leitao@debian.org \
--cc=lenb@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nuno.sa@analog.com \
--cc=orsonzhai@gmail.com \
--cc=paulmck@kernel.org \
--cc=pedro.pbg@usp.br \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saket.dumbre@intel.com \
--cc=tony.luck@intel.com \
--cc=xueshuai@linux.alibaba.com \
--cc=zhang.lyra@gmail.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