From: Linus Walleij <linus.walleij@linaro.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Robert Jarzmik <robert.jarzmik@free.fr>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [RFC/RFT PATCH 1/3] gpio: tegra: remove gpio_to_irq() from hw irq handlers
Date: Tue, 1 Aug 2017 09:49:14 +0200 [thread overview]
Message-ID: <CACRpkdYoTZHsGbnpoam59XBhD-_AmCP8p96AzQbp-KDoKOdaQA@mail.gmail.com> (raw)
In-Reply-To: <20170708224413.18281-2-grygorii.strashko@ti.com>
On Sun, Jul 9, 2017 at 12:44 AM, Grygorii Strashko
<grygorii.strashko@ti.com> wrote:
> gpio_to_irq() API expected to be used by GPIO consumers and
> not drivers and there are no guarantee that its gpiolib implementation
> is irq safe.
>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Patch applied.
This is obviously the right way to do it.
Tegra people: please test.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-08-01 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 22:44 [RFC/RFT PATCH 0/3] gpiolib: make gpio irqchip compatible with sparse_irq Grygorii Strashko
2017-07-08 22:44 ` [RFC/RFT PATCH 1/3] gpio: tegra: remove gpio_to_irq() from hw irq handlers Grygorii Strashko
2017-08-01 7:49 ` Linus Walleij [this message]
2017-07-08 22:44 ` [RFC/RFT PATCH 2/3] gpio: pxa: " Grygorii Strashko
[not found] ` <20170708224413.18281-3-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2017-08-01 7:47 ` Linus Walleij
[not found] ` <CACRpkdZMgd7hSc6LwO5MbPb3vetd+qZ_5mXB1P9SM-HR+h_Pqg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-01 18:41 ` Robert Jarzmik
2017-07-08 22:44 ` [RFC/RFT PATCH 3/3] gpiolib: make gpio irqchip compatible with sparse_irq Grygorii Strashko
2017-08-01 7:46 ` 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=CACRpkdYoTZHsGbnpoam59XBhD-_AmCP8p96AzQbp-KDoKOdaQA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=jbrunet@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=thierry.reding@gmail.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 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).