Re: [PATCH v3 0/3] Init device ids from ACPI of_compatible

2017-01-24 Thread Andy Shevchenko
On Tue, Jan 24, 2017 at 5:11 PM, Jarkko Nikula wrote: > After addressing comments from Andy > > Reviewed-by: Jarkko Nikula > Tested-by: Jarkko Nikula > - > Intel Finland Oy > Registered Address: PL 281, 00181 Helsinki Business I

Re: [PATCH v3 0/3] Init device ids from ACPI of_compatible

2017-01-24 Thread Jarkko Nikula
On 01/23/2017 06:08 PM, Dan O'Donovan wrote: (Re-submitting this patch set originally created by Leonard Crestez, possibly abandoned by Leonard due to a change in employment) When using devicetree, stuff like i2c_client.name or spi_device.modalias is initialized to the first DT compatible id wit

Re: [PATCH v3 0/3] Init device ids from ACPI of_compatible

2017-01-23 Thread Andy Shevchenko
On Mon, Jan 23, 2017 at 6:08 PM, Dan O'Donovan wrote: > (Re-submitting this patch set originally created by Leonard Crestez, > possibly abandoned by Leonard due to a change in employment) > > When using devicetree, stuff like i2c_client.name or spi_device.modalias > is initialized to the first DT

[PATCH v3 0/3] Init device ids from ACPI of_compatible

2017-01-23 Thread Dan O'Donovan
(Re-submitting this patch set originally created by Leonard Crestez, possibly abandoned by Leonard due to a change in employment) When using devicetree, stuff like i2c_client.name or spi_device.modalias is initialized to the first DT compatible id with the vendor prefix stripped. Since some driver