All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
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, 02 Aug 2015 16:55:23 +0300	[thread overview]
Message-ID: <1480181438523723@web3j.yandex.ru> (raw)
In-Reply-To: <CAMuHMdVWeK0chrG_NZ6diHyBxa13WnesgNZ7gh6dTAENw2bg_A@mail.gmail.com>

Hi Geert

02.08.2015, 15:11, "Geert Uytterhoeven" <geert@linux-m68k.org>:
>>>  - 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.

Ok, I see.
Thanks for clarification

Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-08-02 14:02 UTC|newest]

Thread overview: 26+ 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 04/11] net: phy: " 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 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-02  9:09   ` Geert Uytterhoeven
2015-08-11  7:22   ` Tomi Valkeinen
2015-08-11  7:22     ` Tomi Valkeinen
2015-08-11  7:28     ` Geert Uytterhoeven
2015-08-11  7:28       ` Geert Uytterhoeven
2015-08-02  9:09 ` [PATCH v2 11/11] net: rfkill: " Geert Uytterhoeven
2015-08-13  8:49   ` Johannes Berg
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
2015-08-02 13:55       ` Evgeniy Polyakov [this message]
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=1480181438523723@web3j.yandex.ru \
    --to=zbr@ioremap.net \
    --cc=geert@linux-m68k.org \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.