From: Linus Walleij <linus.walleij@linaro.org>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Alexandre Courbot <acourbot@nvidia.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] gpio: remove gpio_descs global array
Date: Tue, 2 Dec 2014 14:26:20 +0100 [thread overview]
Message-ID: <CACRpkda9PbzEOpYABFy46pqow2yyhWJ0iE71GhAS61j5odZArw@mail.gmail.com> (raw)
In-Reply-To: <CAAVeFuJm_UXHioENBg6himgZkEmopr=T8iCbt0xD6-ds6AHyxA@mail.gmail.com>
On Tue, Dec 2, 2014 at 2:25 PM, Alexandre Courbot <gnurou@gmail.com> wrote:
> On Tue, Dec 2, 2014 at 7:32 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>> This patch changes a return value from -EPROBE_DEFER to -EINVAL in
>> regulator-gpio when a GPIO cannot be found yet, causing probe failures
>> on r8a7791/koelsch:
>
> Hi Geert,
>
> Thanks for signaling this. I think I understand what is going wrong
> and will send a fixup patch in a few minutes.
OK standing by.
Yours,
Linus Walleij
next prev parent reply other threads:[~2014-12-02 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 7:51 [PATCH] gpio: remove gpio_descs global array Alexandre Courbot
2014-11-28 10:29 ` Linus Walleij
2014-12-02 10:32 ` Geert Uytterhoeven
2014-12-02 13:25 ` Alexandre Courbot
2014-12-02 13:26 ` Linus Walleij [this message]
2014-12-02 13:42 ` [PATCH] gpio: fix deferred probe detection for legacy API Alexandre Courbot
2014-12-02 14:11 ` Geert Uytterhoeven
2014-12-02 14:15 ` [PATCH v2] " Alexandre Courbot
2014-12-02 14:30 ` Geert Uytterhoeven
2014-12-02 14:48 ` Linus Walleij
2014-12-02 14:19 ` [PATCH] " Linus Walleij
2014-12-02 14:20 ` Alexandre Courbot
2014-12-02 14:22 ` Alexandre Courbot
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=CACRpkda9PbzEOpYABFy46pqow2yyhWJ0iE71GhAS61j5odZArw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=acourbot@nvidia.com \
--cc=geert@linux-m68k.org \
--cc=gnurou@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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 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).