[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d966a55e-65e0-cbb0-6c4e-4339f577b18e@roeck-us.net>
Date: Fri, 7 May 2021 06:34:33 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>
Cc: Jonathan Cameron <jic23@...nel.org>, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel test robot <lkp@...el.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Hans de Goede <hdegoede@...hat.com>
Subject: Re: [PATCH v2] iio: bme680_i2c: Remove ACPI support
On 5/7/21 2:31 AM, Jonathan Cameron wrote:
> On Wed, 5 May 2021 20:43:32 -0700
> Guenter Roeck <linux@...ck-us.net> wrote:
>
>> With CONFIG_ACPI=n and -Werror, 0-day reports:
>>
>> drivers/iio/chemical/bme680_i2c.c:46:36: error:
>> 'bme680_acpi_match' defined but not used
>>
>> Apparently BME0680 is not a valid ACPI ID. Remove it and with it
>> ACPI support from the bme680_i2c driver.
>>
>> Reported-by: kernel test robot <lkp@...el.com>
>> Cc: Andy Shevchenko <andy.shevchenko@...il.com>
>> Cc: Hans de Goede <hdegoede@...hat.com>
>> Signed-off-by: Guenter Roeck <linux@...ck-us.net>
>
> A note for these is that I'll change the patch titles when applying.
> We aren't removing ACPI support from the drivers, we are simply
> removing the ACPI ID table entries. For most of these PRP0001 magic
> will work just fine with the OF table. That's probably the
> right way for small companies etc to use these in products without
> having to jump through the hoops of getting an ACPI ID.
>
Ok, no problem. I'll keep that in mind if I hit any others.
Thanks,
Guenter
Powered by blists - more mailing lists