On Tue, Jun 30, 2020 at 3:33 PM Lee Jones <lee.jones@xxxxxxxxxx> wrote:
> ... as is the case when !CONFIG_ACPI.
>
> Fixes the following W=1 kernel build warning:
>
> drivers/gpio/gpio-mlxbf2.c:312:36: warning: ‘mlxbf2_gpio_acpi_match’ defined but not used [-Wunused-const-variable=]
> 312 | static const struct acpi_device_id mlxbf2_gpio_acpi_match[] = {
> | ^~~~~~~~~~~~~~~~~~~~~~
>
> Cc: Asmaa Mnebhi <Asmaa@xxxxxxxxxxxx>
> Signed-off-by: Lee Jones <lee.jones@xxxxxxxxxx>
Patch applied!
Yours,
Linus Walleij
Re: [PATCH 09/10] gpio: gpio-mlxbf2: Tell the compiler that ACPI functions may not be use
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 09/10] gpio: gpio-mlxbf2: Tell the compiler that ACPI functions may not be use
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Wed, 8 Jul 2020 09:22:19 +0200
- In-reply-to: <20200630133345.2232932-10-lee.jones@linaro.org>
- References: <20200630133345.2232932-1-lee.jones@linaro.org> <20200630133345.2232932-10-lee.jones@linaro.org>
- References:
- [PATCH 00/10] Clean GPIO of W=1 warnings
- From: Lee Jones
- [PATCH 09/10] gpio: gpio-mlxbf2: Tell the compiler that ACPI functions may not be use
- From: Lee Jones
- [PATCH 00/10] Clean GPIO of W=1 warnings
- Prev by Date: Re: [PATCH 08/10] gpio: gpio-mlxbf: Tell the compiler that ACPI functions may not be used
- Next by Date: Re: [PATCH 10/10] gpio: gpio-mlxbf2.c: Provide __releases() annotation to stop confusing Sparse
- Previous by thread: RE: [PATCH 09/10] gpio: gpio-mlxbf2: Tell the compiler that ACPI functions may not be use
- Next by thread: [PATCH 08/10] gpio: gpio-mlxbf: Tell the compiler that ACPI functions may not be used
- Index(es):
 |