Re: [PATCH v3 1/3] ACPI / utils: Introduce acpi_dev_get_first_match_name()

["Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>]

On Monday, January 8, 2018 2:09:20 PM CET Andy Shevchenko wrote:
> On Sat, 2018-01-06 at 00:27 +0100, Rafael J. Wysocki wrote:
> > On Fri, Jan 5, 2018 at 5:09 PM, Andy Shevchenko
> > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote:
> > > Sometimes the user wants to have device name of the match rather
> > > than
> > > just checking if device present or not. To make life easier for such
> > > users introduce acpi_dev_get_first_match_name() helper based on code
> > > for acpi_dev_present().
> > > 
> > > For example, GPIO driver for Intel Merrifield needs to know the
> > > device
> > > name of pin control to be able to apply GPIO mapping table to the
> > > proper
> > > device.
> > > 
> > > To be more consistent with the purpose rename
> > > 
> > >   struct acpi_dev_present_info  -> struct acpi_dev_match_info
> > >   acpi_dev_present_cb()         -> acpi_dev_match_cb()
> > > 
> > > in the utils.c file.
> > > 
> > > Tested-by: Pierre-Louis Bossart <pierre-louis.bossart@xxxxxxxxxxxxxx
> > > m>
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
> > 
> > OK, so which way do you want this to go in?
> 
> If you have no objections, patch 1 may go straight forward to linux-pm
> tree as far as you are okay with the contents.
> 
> I dunno, if Mika's ACK is enough to you to get the second one (patch 2)
> together, otherwise Linus' ACK would be needed or leave it for next
> cycle.
> 
> According to what Mark and Pierre told previously I guess we just
> postpone patch 3 for next cycle.

OK

Linus, can you please have a look at the [2/3] from this lot and let me know
whether or not I can take it?

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html