From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Cédric Le Goater" <clg@kaod.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: Andrew Jeffery <andrew@aj.id.au>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Joel Stanley <joel@jms.id.au>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions
Date: Mon, 20 May 2019 13:09:41 +0200 [thread overview]
Message-ID: <f1ca56fd-c83d-8ad6-29c9-a8fc6af4531c@redhat.com> (raw)
In-Reply-To: <b12201c8-7d5f-2108-6666-75543c38f243@kaod.org>
On 5/20/19 9:47 AM, Cédric Le Goater wrote:
> Hello,
>
> On 5/6/19 4:20 PM, Cédric Le Goater wrote:
>> Hello,
>>
>> Here is a series adding a couple of cleanups to the Aspeed SoCs to
>> prepare ground for extensions and new SoCs.
>>
>> Thanks,
>>
>> C.
>>
>> Changes since v1:
>>
>> - moved enum defining the Aspeed controller names under aspeed_soc.h
>> - removed AspeedSoCInfo 'sdram_base' field
>> - fixed clang compilation
>>
>> Cédric Le Goater (3):
>> aspeed: add a per SoC mapping for the interrupt space
>> aspeed: add a per SoC mapping for the memory space
>
> I think these two patches are fine to go even if Philippe's comments
> are not addressed. There are valid but not a blocker to me.
OK, so:
patches 1 & 2:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Peter, can you apply them?
>
>> aspeed: use sysbus_init_child_obj() to initialize children
>
> Philippe has taken over this patch in a larger series which will go
> through Eduardo's tree, if I understood well the emails. When merged,
> we can try to re-merge the RTC patchset from Joel. I think we made
> things a little more complex than they should have been.
Sorry if I made things more complex. I went on PTO after sending
"hw/arm: Use object_initialize_child for correct reference counting" [*]
then was slow to address Thomas/Markus comments.
Then maybe I should start pinging maintainer more aggressively when my
series are reviewed but not merged, to not delay further developments.
I took note of your comment and will try to keep things simple the next
time.
Regards,
Phil.
>
> Thanks,
>
> C.
next prev parent reply other threads:[~2019-05-20 11:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 14:20 [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions Cédric Le Goater
2019-05-06 14:20 ` [Qemu-devel] [PATCH v2 1/3] aspeed: add a per SoC mapping for the interrupt space Cédric Le Goater
2019-05-06 14:47 ` Philippe Mathieu-Daudé
2019-05-06 14:50 ` Philippe Mathieu-Daudé
2019-05-07 7:25 ` Cédric Le Goater
2019-05-07 5:18 ` Joel Stanley
2019-05-06 14:20 ` [Qemu-devel] [PATCH v2 2/3] aspeed: add a per SoC mapping for the memory space Cédric Le Goater
2019-05-06 14:52 ` Philippe Mathieu-Daudé
2019-05-07 5:19 ` Joel Stanley
2019-05-06 14:20 ` [Qemu-devel] [PATCH v2 3/3] aspeed: use sysbus_init_child_obj() to initialize children Cédric Le Goater
2019-05-07 5:20 ` Joel Stanley
2019-05-07 5:46 ` Philippe Mathieu-Daudé
2019-05-17 10:11 ` Cédric Le Goater
2019-05-20 7:47 ` [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions Cédric Le Goater
2019-05-20 11:09 ` Philippe Mathieu-Daudé [this message]
2019-05-20 13:11 ` Cédric Le Goater
2019-05-20 13:32 ` Cédric Le Goater
2019-05-20 16:32 ` Philippe Mathieu-Daudé
2019-05-23 12:52 ` Peter Maydell
2019-05-23 13:03 ` Cédric Le Goater
2019-05-24 19:09 ` Eduardo Habkost
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=f1ca56fd-c83d-8ad6-29c9-a8fc6af4531c@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).