From: Maxime Coquelin <maxime.coquelin@st.com>
To: Peter Griffin <peter.griffin@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: Chris Ball <chris@printf.net>,
Patrice CHOTARD <patrice.chotard@st.com>,
Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 08/10] ARM: STi: DT: Enable second sdhci controller for stih416 b2020 boards.
Date: Wed, 9 Jul 2014 13:00:20 +0200 [thread overview]
Message-ID: <53BD20C4.2070500@st.com> (raw)
In-Reply-To: <20140709103016.GA5042@griffinp-ThinkPad-X1-Carbon-2nd>
Hi Ulf, Peter,
I will queue the DT patches to my pull request for v3.17.
Peter, I will need it to be rebased anyway.
Thanks,
Maxime
On 07/09/2014 12:30 PM, Peter Griffin wrote:
> Hi Ulf,
>
> Many thanks for looking at this.
>
>>> +
>>> + mmc1: sdhci@fe81f000 {
>>> + status = "okay";
>>> + bus-width = <8>;
>>> + non-removable;
>>> + };
>>> };
>>
>> Hi Peter,
>>
>> I was trying to apply this patchset on my next branch, but the above
>> file /arch/arm/boot/dts/stih416-b2020-revE.dts does not exist. And I
>> don't see it in linux-next either.
>>
>> What tree/patch are this based upon?
>
> The patchset was on top of v3.15-rc1, however since then that file got renamed
> to stih416-b2020e.dts, which went into 3.16 fixes.
>
> See here for more details https://lkml.org/lkml/2014/6/18/241
>
> Would you like me to re-send or can you up fixup?
>
> regards,
>
> Peter.
>
next prev parent reply other threads:[~2014-07-09 11:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 16:07 [PATCH v2 00/10] Add SDHCI support for STMicroelectronics SoCs Peter Griffin
2014-06-04 16:07 ` [PATCH v2 01/10] mmc: sdhci-st: Intial support for ST SDHCI controller Peter Griffin
2014-06-04 16:07 ` [PATCH v2 02/10] mmc: sdhci-st: ST Microelectronics SDHCI binding documentation Peter Griffin
2014-06-04 16:07 ` [PATCH v2 03/10] ARM: STi: DT: Add sdhci pins for stih416 Peter Griffin
2014-06-04 16:07 ` [PATCH v2 04/10] ARM: STi: DT: Add sdhci controller " Peter Griffin
2014-06-04 16:07 ` [PATCH v2 05/10] ARM: STi: DT: Add sdhci pin configuration for stih415 Peter Griffin
2014-06-04 16:07 ` [PATCH v2 07/10] ARM: STi: DT: Enable mmc0 for both stih415 and stih416 SoCs Peter Griffin
2014-06-04 16:07 ` [PATCH v2 08/10] ARM: STi: DT: Enable second sdhci controller for stih416 b2020 boards Peter Griffin
2014-07-09 10:09 ` Ulf Hansson
2014-07-09 10:30 ` Peter Griffin
2014-07-09 11:00 ` Maxime Coquelin [this message]
2014-07-09 12:17 ` Ulf Hansson
[not found] ` <1401898054-686-1-git-send-email-peter.griffin-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-06-04 16:07 ` [PATCH v2 06/10] ARM: STi: DT: Add sdhci controller for stih415 Peter Griffin
2014-06-04 16:07 ` [PATCH v2 09/10] ARM: update multi_v7_defconfig for STI Peter Griffin
2014-06-04 16:07 ` [PATCH v2 10/10] MAINTAINERS: Add sdhci-st file to ARCH/STI architecture Peter Griffin
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=53BD20C4.2070500@st.com \
--to=maxime.coquelin@st.com \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=patrice.chotard@st.com \
--cc=peter.griffin@linaro.org \
--cc=srinivas.kandagatla@gmail.com \
--cc=ulf.hansson@linaro.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).