From: Andre Przywara <andre.przywara@arm.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: A64 board MMC support
Date: Wed, 11 Jan 2017 14:24:38 +0000 [thread overview]
Message-ID: <27630511-d97c-b1ad-ef18-25fa84b6275d@arm.com> (raw)
In-Reply-To: <20170111135139.ktirdwmzhyv3cn2q@lukather>
Hi,
On 11/01/17 13:51, Maxime Ripard wrote:
> Hi,
>
> On Tue, Jan 10, 2017 at 01:22:30AM +0000, Andre Przywara wrote:
>> These patches here go on top of Maxime's latest A64 MMC series and
>> enable the MMC controllers on the boards using the A64 SoC.
>> As the BananaPi-M64 DT now looks different, lets adds support for
>> that board as well, with one major difference to the Pine64 being the eMMC
>> chip.
>>
>> I could't find commit f9ca9b952ee1 Maxime mentioned in his cover letter,
>> so I applied his patches on top of sunxi/for-next and cherry-picked
>> b4b8664d29 to fix the arm64 build.
>
> I'm fine with all your patches. I've queued them in my MMC series, and
> will continue pushing them and / or merging them if it's ok for you.
Yes, please do!
Many thanks!
Cheers,
Andre.
prev parent reply other threads:[~2017-01-11 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 1:22 Andre Przywara
2017-01-10 1:22 ` [PATCH 1/3] arm64: dts: Pine64: add " Andre Przywara
2017-01-10 9:24 ` kbuild test robot
2017-01-10 1:22 ` [PATCH 2/3] arm64: dts: sun50i: add UART1 pin nodes Andre Przywara
2017-01-10 1:22 ` [PATCH 3/3] arm64: dts: add BananaPi-M64 support Andre Przywara
2017-01-10 13:37 ` kbuild test robot
2017-01-11 13:51 ` [PATCH 0/3] arm64: dts: A64 board MMC support Maxime Ripard
2017-01-11 14:24 ` Andre Przywara [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=27630511-d97c-b1ad-ef18-25fa84b6275d@arm.com \
--to=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®