linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2 10/11] w1: Allow compile test of GPIO consumers if !GPIOLIB
Date: Sun, 2 Aug 2015 14:11:32 +0200	[thread overview]
Message-ID: <CAMuHMdVWeK0chrG_NZ6diHyBxa13WnesgNZ7gh6dTAENw2bg_A@mail.gmail.com> (raw)
In-Reply-To: <1214241438507507@web3j.yandex.ru>

Hi Evgeniy,

On Sun, Aug 2, 2015 at 11:25 AM, Evgeniy Polyakov <zbr@ioremap.net> wrote:
> 02.08.2015, 12:09, "Geert Uytterhoeven" <geert@linux-m68k.org>:
>> 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.
>>
>> Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where
>> appropriate.
>
>> - depends on GPIOLIB
>> + depends on GPIOLIB || COMPILE_TEST
>
> Does that mean GPIO subsystem is always available and no additional dependency needed
> when COMPILE_TEST is enabled?

The GPIO subsystem is not always available, but it provides dummy GPIO consumer
functions if GPIOLIB is not enabled.

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-08-02 12:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-02  9:07 [PATCH v2 00/11] gpio: Allow compile test of GPIO consumers if !GPIOLIB Geert Uytterhoeven
2015-08-02  9:08 ` [PATCH v2 01/11] tpm: " Geert Uytterhoeven
2015-08-02  9:09 ` [PATCH v2 02/11] input: " Geert Uytterhoeven
2015-08-04 18:44   ` Dmitry Torokhov
2015-08-02  9:09 ` [PATCH v2 03/11] misc: ti-st: " Geert Uytterhoeven
2015-08-02  9:09 ` [PATCH v2 05/11] power: " Geert Uytterhoeven
2015-08-05  3:49   ` Sebastian Reichel
2015-08-02  9:09 ` [PATCH v2 04/11] net: phy: " Geert Uytterhoeven
2015-08-02  9:09 ` [PATCH v2 06/11] staging: android: " Geert Uytterhoeven
2015-08-02  9:09 ` [PATCH v2 08/11] serial: " Geert Uytterhoeven
2015-08-02  9:09 ` [PATCH v2 07/11] staging: fbtft: " Geert Uytterhoeven
2015-08-02  9:09 ` [PATCH v2 09/11] fbdev: " Geert Uytterhoeven
2015-08-11  7:22   ` Tomi Valkeinen
2015-08-11  7:28     ` Geert Uytterhoeven
2015-08-02  9:09 ` [PATCH v2 10/11] w1: " Geert Uytterhoeven
2015-08-02  9:25   ` Evgeniy Polyakov
2015-08-02 12:11     ` Geert Uytterhoeven [this message]
2015-08-02 13:55       ` Evgeniy Polyakov
2015-08-02  9:09 ` [PATCH v2 11/11] net: rfkill: " Geert Uytterhoeven
2015-08-13  8:49   ` Johannes Berg
2015-08-10 16:01 ` [PATCH v2 00/11] gpio: " Johannes Berg
2015-08-10 16:23   ` Geert Uytterhoeven
2015-08-10 16:29     ` Peter Huewe

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=CAMuHMdVWeK0chrG_NZ6diHyBxa13WnesgNZ7gh6dTAENw2bg_A@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=zbr@ioremap.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).