On Tue, Dec 03, 2024 at 05:23:16PM +0100, Geert Uytterhoeven wrote: > Merely enabling compile-testing should not enable additional > functionality. Sorry for being dumb, but i don't actually see what is wrong here. There are 4 GPIO drivers which have def_bool y COMPILE_TEST is about building as much as possible, in order to find build bugs. So i don't get what you mean by additional functionality. No additional functionality within the MVEBU driver gets enabled by COMPILE_TEST. Andrew
Re: [PATCH] gpio: GPIO_MVEBU should not default to y when compile-testing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] gpio: GPIO_MVEBU should not default to y when compile-testing
- From: Andrew Lunn <andrew@xxxxxxx>
- Date: Tue, 3 Dec 2024 21:13:00 +0100
- In-reply-to: <6b9e55dbf544297d5acf743f6fa473791ab10644.1733242798.git.geert+renesas@glider.be>
- References: <6b9e55dbf544297d5acf743f6fa473791ab10644.1733242798.git.geert+renesas@glider.be>
- Follow-Ups:
- Re: [PATCH] gpio: GPIO_MVEBU should not default to y when compile-testing
- From: Bartosz Golaszewski
- Re: [PATCH] gpio: GPIO_MVEBU should not default to y when compile-testing
- References:
- [PATCH] gpio: GPIO_MVEBU should not default to y when compile-testing
- From: Geert Uytterhoeven
- [PATCH] gpio: GPIO_MVEBU should not default to y when compile-testing
- Prev by Date: Re: [PATCH 1/2] gpio: omap: allow building the module with COMPILE_TEST=y
- Next by Date: Re: [PATCH 1/2] gpio: omap: allow building the module with COMPILE_TEST=y
- Previous by thread: [PATCH] gpio: GPIO_MVEBU should not default to y when compile-testing
- Next by thread: Re: [PATCH] gpio: GPIO_MVEBU should not default to y when compile-testing
- Index(es):
 |