qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] hw/arm/aspeed: Map the UART5 device unconditionally


From: Cédric Le Goater
Subject: Re: [PATCH] hw/arm/aspeed: Map the UART5 device unconditionally
Date: Wed, 30 Sep 2020 12:07:22 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0

On 9/30/20 7:29 AM, Andrew Jeffery wrote:
> 
> 
> On Fri, 18 Sep 2020, at 02:33, Cédric Le Goater wrote:
>> On 9/17/20 6:57 PM, Philippe Mathieu-Daudé wrote:
>>> On 9/16/20 7:51 AM, Cédric Le Goater wrote:
>>>> On 9/15/20 7:23 PM, Philippe Mathieu-Daudé wrote:
>>>>> ping?
>>>>
>>>> It's reviewed : 
>>>>
>>>>   
>>>> 20200905212415.760452-1-f4bug@amsat.org/">http://patchwork.ozlabs.org/project/qemu-devel/patch/20200905212415.760452-1-f4bug@amsat.org/
>>>>
>>>
>>> Yes I know :) This is part of my routine to check if a
>>> patch hasn't been confirmed to be queued 1 week after the
>>> last review, to ping the maintainer (because some
>>> automatically flush patches older than 1month in their
>>> mailbox).
>>
>> ooh. That's brutal.
>>
>>>> I will send a PR when I have more patches.
>>>
>>> Ah OK. I didn't know you would keep merging the Aspeed
>>> patches. Since this was a single patch, I thought it would
>>> go via the usual qemu-arm queue from Peter.
>>
>> sure. It could also. Fine with me. I have only three for the
>> moment. 
>>
>>> No rush, I just wanted to be sure the patch was not lost.
>>> Also, once a patch is queued, I understand it is the
>>> maintainer responsibility to keep rebasing the patch
>>> queued.
>>
>> yes. I know. I have been taking care of Andrew's ADC patches 
>> since 2017 ... cough cough :)
> 
> Agh!

Does that mean "I will work on it !" ? :)

C. 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]