From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] pinctrl: stm32: add STM32F769 MCU support
Date: Tue, 23 Jan 2018 09:44:46 +0100 [thread overview]
Message-ID: <7dd6bae8-87ef-7dd1-477a-a40d6ab48a94@st.com> (raw)
In-Reply-To: <CACRpkdYTbjXx5tx9LjRKkbZ7zCBZz0Fhe_cmRm4DMq_3hTTmtA@mail.gmail.com>
On 01/22/2018 09:25 AM, Linus Walleij wrote:
> On Mon, Dec 11, 2017 at 9:54 AM, Alexandre Torgue
> <alexandre.torgue@st.com> wrote:
>
>> This patch which adds STM32F769 pinctrl and GPIO support, relies on the
>> generic STM32 pinctrl driver.
>>
>> Signed-off-by: Alexandre Torgue <alexandre.torgue@st.com>
>
> Patch applied as Patrice poked me.
>
> I hope it works fine being applied in isolation from the other
> patches?
Yes it does. I will add other patches in my next pull request (for v4.17).
Thanks
Alex
>
> Yours,
> Linus Walleij
>
next prev parent reply other threads:[~2018-01-23 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 8:54 [PATCH 1/5] dt-bindings: pinctrl: Add st, stm32f769-pinctrl compatible to stm32-pinctrl Alexandre Torgue
2017-12-11 8:54 ` [PATCH 2/5] pinctrl: stm32: add STM32F769 MCU support Alexandre Torgue
2018-01-18 14:05 ` Patrice CHOTARD
2018-01-22 8:28 ` Linus Walleij
2018-01-22 8:25 ` Linus Walleij
2018-01-23 8:44 ` Alexandre Torgue [this message]
2017-12-11 8:54 ` [PATCH 3/5] ARM: mach-stm32: Kconfig: introduce MACH_STM32F769 flag Alexandre Torgue
2017-12-11 8:54 ` [PATCH 4/5] ARM: mach-stm32: add new STM32F769 MCU Alexandre Torgue
2017-12-11 8:54 ` [PATCH 5/5] ARM: dts: stm32: use dedicated files for pinctrl on stm32f7 family Alexandre Torgue
2017-12-15 21:47 ` [PATCH 1/5] dt-bindings: pinctrl: Add st,stm32f769-pinctrl compatible to stm32-pinctrl Rob Herring
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=7dd6bae8-87ef-7dd1-477a-a40d6ab48a94@st.com \
--to=alexandre.torgue@st.com \
--cc=linux-arm-kernel@lists.infradead.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