From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/5] ARM: configs: multi_v7: Add I2C support
Date: Fri, 20 Apr 2018 12:07:44 +0200 [thread overview]
Message-ID: <CAMuHMdWwmsOm_LjjhYBFseFa1HaWFCbGEGf+XbZxSSf3JC=vPQ@mail.gmail.com> (raw)
In-Reply-To: <1524215874-15093-2-git-send-email-pierre-yves.mordret@st.com>
Hi Pierre-Yves,
On Fri, Apr 20, 2018 at 11:17 AM, Pierre-Yves MORDRET
<pierre-yves.mordret@st.com> wrote:
> This patch adds I2C F7 support to multi_v7_defconfig
>
> Signed-off-by: Pierre-Yves MORDRET <pierre-yves.mordret@st.com>
Thanks for your patch!
I think the subject should be "ARM: multi_v7_defconfig: Add STM32F7
I2C support",
as generic I2C support is already enabled.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-04-20 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 9:17 [PATCH v1 0/5] Add I2C Support on STM32MP157C Pierre-Yves MORDRET
2018-04-20 9:17 ` [PATCH v1 1/5] ARM: configs: multi_v7: Add I2C support Pierre-Yves MORDRET
2018-04-20 10:07 ` Geert Uytterhoeven [this message]
2018-04-20 9:17 ` [PATCH v1 2/5] ARM: dts: stm32: Add I2C support for STM32MP157C SoC Pierre-Yves MORDRET
2018-04-20 9:17 ` [PATCH v1 3/5] ARM: dts: stm32: Add I2Cs pin control on STM32MP157C Pierre-Yves MORDRET
2018-04-20 9:17 ` [PATCH v1 4/5] ARM: dts: stm32: Add I2C4 support for STM32MP157C-ED1 Pierre-Yves MORDRET
2018-04-20 9:17 ` [PATCH v1 5/5] ARM: dts: stm32: Add I2C2/5 support for STM32MP157C-EV1 Pierre-Yves MORDRET
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='CAMuHMdWwmsOm_LjjhYBFseFa1HaWFCbGEGf+XbZxSSf3JC=vPQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--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;
as well as URLs for NNTP newsgroup(s).