On Mon, Feb 8, 2021 at 3:51 PM Geert Uytterhoeven
<geert+renesas@xxxxxxxxx> wrote:
> Merely enabling CONFIG_COMPILE_TEST should not enable additional code.
> To fix this, restrict the automatic enabling of GPIO_MXS to ARCH_MXS,
> and ask the user in case of compile-testing.
>
> Fixes: 6876ca311bfca5d7 ("gpio: mxs: add COMPILE_TEST support for GPIO_MXS")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
Reviewed-by: Linus Walleij <linus.walleij@xxxxxxxxxx>
Yours,
Linus Walleij
Re: [PATCH] gpio: GPIO_MXS should not default to y, unconditionally
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] gpio: GPIO_MXS should not default to y, unconditionally
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Fri, 12 Feb 2021 13:53:44 +0100
- In-reply-to: <20210208145153.422093-1-geert+renesas@glider.be>
- References: <20210208145153.422093-1-geert+renesas@glider.be>
- References:
- [PATCH] gpio: GPIO_MXS should not default to y, unconditionally
- From: Geert Uytterhoeven
- [PATCH] gpio: GPIO_MXS should not default to y, unconditionally
- Prev by Date: [PATCH v3 3/3] pinctrl: Add Xilinx ZynqMP pinctrl driver support
- Next by Date: RE: [Linuxarm] Re: [PATCH for next v1 1/2] gpio: omap: Replace raw_spin_lock_irqsave with raw_spin_lock in omap_gpio_irq_handler()
- Previous by thread: Re: [PATCH] gpio: GPIO_MXS should not default to y, unconditionally
- Next by thread: RFC: oftree based setup of composite board devices
- Index(es):
 |