From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / gpio: do not fall back to parsing _CRS when we get a deferral
Date: Tue, 28 Mar 2017 16:32:25 +0300 [thread overview]
Message-ID: <20170328133225.GS2957@lahna.fi.intel.com> (raw)
In-Reply-To: <CACRpkdZJxvLF2T4akRVSNa9SjS30_q_A-vd2OaLE4eMSye1EMA@mail.gmail.com>
On Tue, Mar 28, 2017 at 03:25:56PM +0200, Linus Walleij wrote:
> On Thu, Mar 23, 2017 at 9:21 PM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
>
> > If, while locating GPIOs by name, we get probe deferral, we should
> > immediately report it to caller rather than trying to fall back to parsing
> > unnamed GPIOs from _CRS block.
> >
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>
> Can I get some indication from Mika/Rafael/Andy whether this is correct?
Sorry, I saw the patch but then forgot to ack it.
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2017-03-28 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 20:21 [PATCH] ACPI / gpio: do not fall back to parsing _CRS when we get a deferral Dmitry Torokhov
2017-03-28 13:25 ` Linus Walleij
2017-03-28 13:32 ` Mika Westerberg [this message]
2017-03-28 15:03 ` Andy Shevchenko
2017-03-28 15:04 ` Andy Shevchenko
2017-03-29 16:33 ` Hans de Goede
2017-03-29 16:42 ` Andy Shevchenko
2017-03-30 9:08 ` Linus Walleij
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=20170328133225.GS2957@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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.