From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Andrew Jeffery" <andrew@aj.id.au>,
"Cédric Le Goater" <clg@kaod.org>,
qemu-arm@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Joel Stanley <joel@jms.id.au>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] hw/arm: ast2600: Wire up eMMC controller
Date: Fri, 13 Dec 2019 18:04:17 +0100 [thread overview]
Message-ID: <d70b5f1a-08e3-4664-719f-dd5526a4135e@redhat.com> (raw)
In-Reply-To: <1d96ac9b-5eb2-43ec-bf21-334ee3fa4420@www.fastmail.com>
On 12/13/19 8:37 AM, Andrew Jeffery wrote:
> On Fri, 13 Dec 2019, at 18:03, Cédric Le Goater wrote:
>> On 13/12/2019 05:28, Andrew Jeffery wrote:
>>> Hello,
>>>
>>> The AST2600 has an additional SDHCI intended for use as an eMMC boot source.
>>> These two patches rework the existing ASPEED SDHCI model to accommodate the
>>> single-slot nature of the eMMC controller and wire it into the AST2600 SoC.
>>>
>>> v2 contains some minor refactorings in response to issues pointed out by
>>> Cedric.
>>
>>
>> I think these patches are based on mainline. I fixed them locally on
>> my aspeed 5.0 branch and I plan to send them along with other aspeed
>> changes in the 5.0 timeframe.
>
> Yeah, they're based on Peter's tree. I'll base future patches on yours.
To help any reviewer, simply add a note in the cover on which tree your
series is based. This also works with individual patch, add the note
under the '---' separator.
prev parent reply other threads:[~2019-12-13 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 4:28 [PATCH v2 0/2] hw/arm: ast2600: Wire up eMMC controller Andrew Jeffery
2019-12-13 4:28 ` [PATCH v2 1/2] hw/sd: Configure number of slots exposed by the ASPEED SDHCI model Andrew Jeffery
2019-12-13 7:29 ` Cédric Le Goater
2019-12-13 4:28 ` [PATCH v2 2/2] hw/arm: ast2600: Wire up the eMMC controller Andrew Jeffery
2019-12-13 7:30 ` Cédric Le Goater
2019-12-13 7:33 ` [PATCH v2 0/2] hw/arm: ast2600: Wire up " Cédric Le Goater
2019-12-13 7:37 ` Andrew Jeffery
2019-12-13 17:04 ` Philippe Mathieu-Daudé [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=d70b5f1a-08e3-4664-719f-dd5526a4135e@redhat.com \
--to=philmd@redhat.com \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).