Re: [PATCH v5 01/13] notifier: add device-managed registration APIs
Uwe Kleine-König <[email protected]>
| Newsgroups | gmane.linux.acpi.devel,gmane.linux.kernel,gmane.linux.kernel.gpio,gmane.linux.pwm,gmane.linux.kernel.iio,gmane.linux.kernel.input,gmane.linux.drivers.platform.x86.devel |
|---|---|
| Message-ID | <aoQWOsPeyU9o3Ahn@monoceros> |
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 <[email protected]> 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
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmqEF0QACgkQj4D7WH0S /k6+ewf/TQPKKAWHFqB2guxJQb4tJtqqrt9CfxNlHgpRy98IQr+Wzsclp/2b55PD +Vt8rK1QzYpoCbHNgn48yp+ZwOgUgZLGuFt1oOMJuz4TML4VoRQW/KQBjYb8RH6h bZwXKf20jhh0jcWWdq+Oloo7khDa3AfPjzRMezSt63HtWnFWyDBFmk+Hpj2iK5wV ydEynNxomqrfrzujN4nShzkby6/nearXk+4xXCvj02C50nfaHCtzBWc07ic2TP90 xDPXfb0bl2EHmQ7jRNKDBne2D3J7gm+NVDzSblze4JXAuRSbDl51QXnnQ49Me8pn JJE4fMKe0QjKuFoPX4pzR1Up39HZcg== =T8Ew -----END PGP SIGNATURE-----