linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
	Arnd Bergmann <arnd@arndb.de>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>,
	linux-gpio@vger.kernel.org, linux-leds@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH 0/3] leds: leds-gpio: Allow compile test if !GPIOLIB
Date: Thu,  7 May 2015 10:08:07 +0200	[thread overview]
Message-ID: <1430986090-7243-1-git-send-email-geert@linux-m68k.org> (raw)

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 allows compile testing of the leds-gpio driver if
GPIOLIB is not enabled. This requires adding a missing dummy to gpiolib,
and a missing include to leds-gpio.

This series follows the work started in the series "[PATCH 00/27] gpio:
Allow compile test of GPIO consumers if !GPIOLIB"
(https://lkml.org/lkml/2015/5/5/779), but can be applied independently.

The third patch depends on the first two patches, but it could be folded
into "[PATCH 09/27] leds: Allow compile test of GPIO consumers if
!GPIOLIB" of the series mentioned above, once its dependencies are
satisfied.

Thanks!

Geert Uytterhoeven (3):
  gpiolib: Add missing dummies for the unified device properties
    interface
  leds: leds-gpio: Add missing #include <linux/of.h>
  leds: leds-gpio: Allow compile test if !GPIOLIB

 drivers/leds/Kconfig          |  2 +-
 drivers/leds/leds-gpio.c      |  1 +
 include/linux/gpio/consumer.h | 15 +++++++++++++++
 3 files changed, 17 insertions(+), 1 deletion(-)

-- 
1.9.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

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

             reply	other threads:[~2015-05-07  8:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07  8:08 Geert Uytterhoeven [this message]
2015-05-07  8:08 ` [PATCH 1/3] gpiolib: Add missing dummies for the unified device properties interface Geert Uytterhoeven
2015-05-08 17:43   ` Bryan Wu
2015-05-12  7:48     ` Geert Uytterhoeven
2015-05-12  7:47   ` Alexandre Courbot
2015-05-12 10:31   ` Linus Walleij
2015-05-12 17:48     ` Bryan Wu
2015-05-07  8:08 ` [PATCH 2/3] leds: leds-gpio: Add missing #include <linux/of.h> Geert Uytterhoeven
2015-05-07 12:15   ` Jacek Anaszewski
2015-05-12 17:49     ` Bryan Wu
2015-05-07  8:08 ` [PATCH 3/3] leds: leds-gpio: Allow compile test if !GPIOLIB Geert Uytterhoeven
2015-05-07 12:15   ` Jacek Anaszewski
2015-05-12 10:23   ` Linus Walleij
2015-05-12 17:53     ` Bryan Wu

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=1430986090-7243-1-git-send-email-geert@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=cooloney@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=j.anaszewski@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).