From: Linus Walleij <linus.walleij@linaro.org>
To: Alexandre TORGUE <alexandre.torgue@st.com>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Patrice Chotard <patrice.chotard@st.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Rob Herring <robh+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] pinctrl: stm32: set pin to gpio input when used as interrupt
Date: Wed, 31 May 2017 02:05:12 +0200 [thread overview]
Message-ID: <CACRpkdbp1tbBhhd+ttBYApB0dOKx_N3U42cEb6r7wgVLJdRoyw@mail.gmail.com> (raw)
In-Reply-To: <1496074653-2941-2-git-send-email-alexandre.torgue@st.com>
On Mon, May 29, 2017 at 6:17 PM, Alexandre TORGUE
<alexandre.torgue@st.com> wrote:
> This patch ensures that pin is correctly set as gpio input when it is used
> as an interrupt.
>
> Signed-off-by: Alexandre TORGUE <alexandre.torgue@st.com>
Nice!
Patch applied.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-05-31 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 16:17 [PATCH v2 0/3] Add fixes to STM32 pintrl Alexandre TORGUE
[not found] ` <1496074653-2941-1-git-send-email-alexandre.torgue-qxv4g6HH51o@public.gmane.org>
2017-05-29 16:17 ` [PATCH v2 1/3] pinctrl: stm32: set pin to gpio input when used as interrupt Alexandre TORGUE
2017-05-31 0:05 ` Linus Walleij [this message]
2017-05-29 16:17 ` [PATCH v2 2/3] pinctrl: stm32: Implement .get_direction gpio_chip callback Alexandre TORGUE
[not found] ` <1496074653-2941-3-git-send-email-alexandre.torgue-qxv4g6HH51o@public.gmane.org>
2017-05-31 0:06 ` Linus Walleij
2017-05-29 16:17 ` [PATCH v2 3/3] ARM: dts: stm32: Set gpio controller also as interrupt controller Alexandre TORGUE
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=CACRpkdbp1tbBhhd+ttBYApB0dOKx_N3U42cEb6r7wgVLJdRoyw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@st.com \
--cc=paul.gortmaker@windriver.com \
--cc=robh+dt@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).