From: Alexandre Torgue <alexandre.torgue@st.com>
To: "Yannick Fertré" <yannick.fertre@st.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Benjamin Gaignard" <benjamin.gaignard@st.com>,
"Philippe Cornu" <philippe.cornu@st.com>,
"Fabrice Gasnier" <fabrice.gasnier@st.com>
Subject: Re: [PATCH v1 0/2] enable display on stm32mp157c-dk1 board
Date: Tue, 21 May 2019 12:22:04 +0200 [thread overview]
Message-ID: <5864f09f-4cd3-cadc-2210-4946142e582d@st.com> (raw)
In-Reply-To: <1553863438-6720-1-git-send-email-yannick.fertre@st.com>
Hi Yannick
On 3/29/19 1:43 PM, Yannick Fertré wrote:
> Enable display on stm32mp157c-dk1 board. I2c node must be created first.
>
> Yannick Fertré (2):
> ARM: dts: stm32: Add I2C 1 and 4 config for stm32mp157a-dk1
> ARM: dts: stm32: enable display on stm32mp157c-dk1 board
>
> arch/arm/boot/dts/stm32mp157a-dk1.dts | 78 +++++++++++++++++++++++++++++++++++
> 1 file changed, 78 insertions(+)
>
> --
> 2.7.4
>
Series applied on stm32-next.
Regards
Alex
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-05-21 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 12:43 [PATCH v1 0/2] enable display on stm32mp157c-dk1 board Yannick Fertré
2019-03-29 12:43 ` [PATCH v1 1/2] ARM: dts: stm32: Add I2C 1 and 4 config for stm32mp157a-dk1 Yannick Fertré
2019-03-29 12:43 ` [PATCH v1 2/2] ARM: dts: stm32: enable display on stm32mp157c-dk1 board Yannick Fertré
2019-05-21 10:22 ` Alexandre Torgue [this message]
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=5864f09f-4cd3-cadc-2210-4946142e582d@st.com \
--to=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=philippe.cornu@st.com \
--cc=robh+dt@kernel.org \
--cc=yannick.fertre@st.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).