From: Rob Herring <robh@kernel.org>
To: patrice.chotard@st.com
Cc: mark.rutland@arm.com, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
alexandre.torgue@st.com, lee.jones@linaro.org,
mcoquelin.stm32@gmail.com
Subject: Re: [PATCH v2 5/6] dt-bindings: mfd: Add STM32F7 SDMMC2 rcc entry
Date: Mon, 5 Mar 2018 20:38:06 -0600 [thread overview]
Message-ID: <20180306023806.rhmpp7lwftgb74un@rob-hp-laptop> (raw)
In-Reply-To: <1519901623-23216-6-git-send-email-patrice.chotard@st.com>
On Thu, Mar 01, 2018 at 11:53:42AM +0100, patrice.chotard@st.com wrote:
> From: Patrice Chotard <patrice.chotard@st.com>
>
> STM32F769 SoC provides 2 SDMMC instances, add missing
> RCC SDMMC2 entry for it.
>
> Signed-off-by: Patrice Chotard <patrice.chotard@st.com>
> ---
> include/dt-bindings/mfd/stm32f7-rcc.h | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-03-06 2:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 10:53 [PATCH v2 0/6] Add mmc support for STM32F7 boards patrice.chotard
2018-03-01 10:53 ` [PATCH v2 1/6] ARM: dts: stm32: Add sdio pins definition for stm32f7 patrice.chotard
2018-03-01 10:53 ` [PATCH v2 2/6] ARM: dts: stm32: Enable sdio1 for stm32f746-disco patrice.chotard
2018-03-01 10:53 ` [PATCH v2 3/6] ARM: dts: stm32: Enable sdio1 for stm32f746-eval patrice.chotard
2018-03-01 10:53 ` [PATCH v2 4/6] ARM: dts: stm32: Enable sdio1 for stm32f769-disco patrice.chotard
2018-03-06 2:37 ` Rob Herring
2018-03-01 10:53 ` [PATCH v2 5/6] dt-bindings: mfd: Add STM32F7 SDMMC2 rcc entry patrice.chotard
2018-03-06 2:38 ` Rob Herring [this message]
2018-03-01 10:53 ` [PATCH v2 6/6] ARM: dts: stm32: Fix sdio2 rcc hard coded value patrice.chotard
2018-03-05 8:43 ` [PATCH v2 0/6] Add mmc support for STM32F7 boards Alexandre Torgue
2018-03-07 8:35 ` Lee Jones
2018-03-07 9:11 ` Patrice CHOTARD
2018-03-07 10:57 ` Lee Jones
2018-03-08 12:51 ` 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=20180306023806.rhmpp7lwftgb74un@rob-hp-laptop \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@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