All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"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 15:11:19 +0200	[thread overview]
Message-ID: <270e510b-687a-6b43-8cd6-c1eb1aea41e6@kaod.org> (raw)
In-Reply-To: <f1ca56fd-c83d-8ad6-29c9-a8fc6af4531c@redhat.com>

Hello,

On 5/20/19 1:09 PM, Philippe Mathieu-Daudé wrote:
> 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

PTO ?

> "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.

Well, I don't know if there is a good method for transversal patchsets 
like this one. I guess it depends on the area. 

The overall merging process became more complex that expected after our 
three simple patchsets (Yours, Joel's and mine) collided. 
 
> I took note of your comment and will try to keep things simple the next
> time.

It's not a big issue. We have time to provide fixes before 4.1 is out. 
Let's put some energy to move on and get code merged.

Peter, 

do you want me to resend with only the two first patches and include 
Joel's in the same series ? I would leave out the part Philippe is 
covering in his object_initialize_child() patchset.

Thanks,

C.



  reply	other threads:[~2019-05-20 13:12 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é
2019-05-20 13:11     ` Cédric Le Goater [this message]
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=270e510b-687a-6b43-8cd6-c1eb1aea41e6@kaod.org \
    --to=clg@kaod.org \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.