Re: [PATCH v4 00/35] Remove .notify callback in acpi_device_ops

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jun 5, 2023 at 11:39 AM Wilczynski, Michal
<michal.wilczynski@xxxxxxxxx> wrote:
> On 6/3/2023 1:03 PM, andy.shevchenko@xxxxxxxxx wrote:
> > Thu, Jun 01, 2023 at 03:16:55PM +0200, Michal Wilczynski kirjoitti:
> >> Currently drivers support ACPI event handlers by defining .notify
> >> callback in acpi_device_ops. This solution is suboptimal as event
> >> handler installer installs intermediary function acpi_notify_device as a
> >> handler in every driver. Also this approach requires extra variable
> >> 'flags' for specifying event types that the driver want to subscribe to.
> >> Additionally this is a pre-work required to align acpi_driver with
> >> platform_driver and eventually replace acpi_driver with platform_driver.
> >>
> >> Remove .notify callback from the acpi_device_ops. Replace it with each
> >> driver installing and removing it's event handlers.
> > Somehow this thread is screwed up in a sense of linking messages.
> > Even on the archives there are rather individual patches.
> >
> > Please, be sure you are always use --thread when formatting it.
> > Yet you have a possibility to Cc different patches to the different
> > mailing lists and people.
>
> Hi,
> Thank you for this remark, I was trying to be clever and tried to send a patch
> in a bit non-canonical way. So I've send a cover letter and a couple of other
> major bits of a solution to everyone from the output of scripts/get_maintainer.pl
> run on every patch from this series.
>
> ./scripts/get_maintainer.pl /home/mwilczyn/patches/remove_notify_external/*
>
> (where remove_notify_external contains all patches generated for this patchset)
>
> For the rest I used --to-cmd and --cc-cmd options of git send-email. This way I could
> send patches with minor changes to every driver to only specified people marked
> by get_maintainer.pl for this individual patch.
>
> Hope that when re-sending with next revision --thread can help.

You can send it to yourself first to test.

The biggest issue with your thread is making `b4` unable to catch the
thread. Since it cooperates with lore archive, it's extremely hard to
see the whole thing via the web either.

-- 
With Best Regards,
Andy Shevchenko




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Input]     [Linux Kernel]     [Linux SCSI]     [X.org]

  Powered by Linux