From: Wolfram Sang <wsa@the-dreams.de>
To: Bich HEMON <bich.hemon@st.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
Pierre Yves MORDRET <pierre-yves.mordret@st.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: i2c-stm32: update optional properties for stm32h7/stm32mp1
Date: Sun, 24 Mar 2019 23:15:14 +0100 [thread overview]
Message-ID: <20190324221514.GD6934@kunai> (raw)
In-Reply-To: <1551885100-22207-3-git-send-email-bich.hemon@st.com>
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
On Wed, Mar 06, 2019 at 03:11:51PM +0000, Bich HEMON wrote:
> Add STM32H7 and STM32MP1 in the list of compatible socs for each
> optional property.
>
> Signed-off-by: Bich Hemon <bich.hemon@st.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-03-24 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 15:11 [PATCH 0/2] Patches for i2c-stm32 device tree bindings Bich HEMON
2019-03-06 15:11 ` [PATCH 1/2] dt-bindings: i2c-stm32: remove extra spaces Bich HEMON
2019-03-21 8:28 ` Pierre Yves MORDRET
2019-03-24 22:15 ` Wolfram Sang
2019-03-06 15:11 ` [PATCH 2/2] dt-bindings: i2c-stm32: update optional properties for stm32h7/stm32mp1 Bich HEMON
2019-03-21 8:28 ` Pierre Yves MORDRET
2019-03-24 22:15 ` Wolfram Sang [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=20190324221514.GD6934@kunai \
--to=wsa@the-dreams.de \
--cc=alexandre.torgue@st.com \
--cc=bich.hemon@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.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=pierre-yves.mordret@st.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).