All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jonathan Cameron <jic23@kernel.org>,
	linux-iio <linux-iio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] iio: bme680_i2c: Make bme680_acpi_match depend on CONFIG_ACPI
Date: Tue, 4 May 2021 20:46:29 +0300	[thread overview]
Message-ID: <CAHp75VdOPkRrAWo9tFvN-9HhXfCGo8hA7V0jypPiLnibUCbuVw@mail.gmail.com> (raw)
In-Reply-To: <CAHp75Vd-iTkA5Y6tEHtfcqLxxmHaaU8nLQSL7eWb-gaa-c8AJg@mail.gmail.com>

On Tue, May 4, 2021 at 8:44 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Tue, May 4, 2021 at 8:40 PM Guenter Roeck <linux@roeck-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
>
> > Given the other patch, question of course is if this ACPI ID
> > is real. A Google search suggests that this might not be the case.
> > Should we remove it as well ? STK8312 has the same problem.
>
> For this one definitely removal. Looking into the code it suggests a
> cargo cult taken that time by a few contributors to invent fake ACPI
> IDs while submitting new drivers.
> Feel free to add my tag or if you wish me I'll add it explicitly.

Had just looked at STK, the same guy as for AOS2315. So, also to remove.

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2021-05-04 17:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 17:40 [PATCH] iio: bme680_i2c: Make bme680_acpi_match depend on CONFIG_ACPI Guenter Roeck
2021-05-04 17:44 ` Andy Shevchenko
2021-05-04 17:46   ` Andy Shevchenko [this message]
2021-05-04 18:00   ` Guenter Roeck
2021-05-05  8:32     ` Jonathan Cameron
2021-05-05  8:34       ` Jonathan Cameron
2021-05-05 13:00         ` Guenter Roeck
2021-05-05 13:22         ` Andy Shevchenko
2021-05-05 13:39           ` Hans de Goede
2021-05-05 13:53             ` Andy Shevchenko
2021-05-05 14:04               ` Hans de Goede
2021-05-05 14:18                 ` Andy Shevchenko
2021-05-05 15:19                   ` Hans de Goede
2021-05-05 16:26                     ` Andy Shevchenko
2021-05-05 16:30                       ` Hans de Goede
2021-05-07 11:53           ` Pavel Machek
2021-05-07 12:39             ` Andy Shevchenko
2021-05-05  9:04       ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHp75VdOPkRrAWo9tFvN-9HhXfCGo8hA7V0jypPiLnibUCbuVw@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkp@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.