Hi all,
The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is
not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer
functionality only, can still be compiled if GPIOLIB is not enabled.
This patch series relaxes the dependencies on GPIOLIB if COMPILE_TEST is
enabled, where appropriate.
There are a few more drivers that depend on GPIOLIB and that may be
eligible for COMPILE_TEST. These I didn't handle yet, as I couldn't
enable them with m68k/all{mod,yes}config due to other dependencies.
This series is the remaining part of ("[PATCH 00/27] gpio: Allow compile
test of GPIO consumers if !GPIOLIB", https://lkml.org/lkml/2015/5/5/779),
updated for new config symbols up to v4.2-rc4. It applies to
next-20150731.
Thanks for applying!
Geert Uytterhoeven (11):
tpm: Allow compile test of GPIO consumers if !GPIOLIB
input: Allow compile test of GPIO consumers if !GPIOLIB
misc: ti-st: Allow compile test of GPIO consumers if !GPIOLIB
net: phy: Allow compile test of GPIO consumers if !GPIOLIB
power: Allow compile test of GPIO consumers if !GPIOLIB
staging: android: Allow compile test of GPIO consumers if !GPIOLIB
staging: fbtft: Allow compile test of GPIO consumers if !GPIOLIB
serial: Allow compile test of GPIO consumers if !GPIOLIB
fbdev: Allow compile test of GPIO consumers if !GPIOLIB
w1: Allow compile test of GPIO consumers if !GPIOLIB
net: rfkill: Allow compile test of GPIO consumers if !GPIOLIB
drivers/char/tpm/st33zp24/Kconfig | 2 +-
drivers/input/keyboard/Kconfig | 4 ++--
drivers/input/misc/Kconfig | 11 ++++++-----
drivers/input/mouse/Kconfig | 2 +-
drivers/input/touchscreen/Kconfig | 8 ++++----
drivers/misc/ti-st/Kconfig | 3 ++-
drivers/net/phy/Kconfig | 3 ++-
drivers/power/Kconfig | 17 +++++++++++------
drivers/staging/android/Kconfig | 3 ++-
drivers/staging/fbtft/Kconfig | 3 ++-
drivers/tty/serial/Kconfig | 3 ++-
drivers/video/fbdev/Kconfig | 2 +-
drivers/w1/masters/Kconfig | 2 +-
net/rfkill/Kconfig | 3 ++-
14 files changed, 39 insertions(+), 27 deletions(-)
--
1.9.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
On Sun, 2015-08-02 at 11:07 +0200, Geert Uytterhoeven wrote:
>
> Thanks for applying!
>
Did you expect the series to get applied somewhere (GPIO tree, if
there's such a thing?), or the single patches to go through the
relevant other trees?
Fine with me either way, but it'd be good to know so we don't have the
patches twice :)
johannes
Hi Johannes,
On Mon, Aug 10, 2015 at 6:01 PM, Johannes Berg
<[email protected]> wrote:
> On Sun, 2015-08-02 at 11:07 +0200, Geert Uytterhoeven wrote:
>> Thanks for applying!
>
> Did you expect the series to get applied somewhere (GPIO tree, if
> there's such a thing?), or the single patches to go through the
> relevant other trees?
>
> Fine with me either way, but it'd be good to know so we don't have the
> patches twice :)
I'd like the individual subsystem maintainers to apply the respective
patches. Sorry for being unclear.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Am 10. August 2015 18:23:52 MESZ, schrieb Geert Uytterhoeven <[email protected]>:
>
>I'd like the individual subsystem maintainers to apply the respective
>patches. Sorry for being unclear.
Okay, thanks for the clarification.
I'll apply the TPM patch.
Peter
--
Sent from my mobile