[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gTUNV4vSF7RxQf9XB8gfOSwOX=+pg7jZVw_yTYbRdp5Q@mail.gmail.com>
Date: Tue, 17 Oct 2023 12:55:55 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "Wilczynski, Michal" <michal.wilczynski@...el.com>
Cc: linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
nvdimm@...ts.linux.dev,
"Williams, Dan J" <dan.j.williams@...el.com>,
rafael.j.wysocki@...el.com, andriy.shevchenko@...el.com,
lenb@...nel.org, vishal.l.verma@...el.com, ira.weiny@...el.com
Subject: Re: [PATCH v2 5/6] ACPI: NFIT: Replace acpi_driver with platform_driver
On Tue, Oct 17, 2023 at 12:45 PM Wilczynski, Michal
<michal.wilczynski@...el.com> wrote:
>
>
> On 10/6/2023 7:30 PM, Michal Wilczynski wrote:
> > NFIT driver uses struct acpi_driver incorrectly to register itself.
> > This is wrong as the instances of the ACPI devices are not meant
> > to be literal devices, they're supposed to describe ACPI entry of a
> > particular device.
> >
> > Use platform_driver instead of acpi_driver. In relevant places call
> > platform devices instances pdev to make a distinction with ACPI
> > devices instances.
> >
> > NFIT driver uses devm_*() family of functions extensively. This change
> > has no impact on correct functioning of the whole devm_*() family of
> > functions, since the lifecycle of the device stays the same. It is still
> > being created during the enumeration, and destroyed on platform device
> > removal.
> >
> > Suggested-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> > Signed-off-by: Michal Wilczynski <michal.wilczynski@...el.com>
>
> Hi Dan,
> Rafael already reviewed this patch series and merged patches
> that he likes. We're waiting on your input regarding two NFIT
> commits in this series.
I actually haven't looked at the NFIT patches in this series myself
and this is not urgent at all IMV.
Thanks!
Powered by blists - more mailing lists