From: "Cédric Le Goater" <clg@kaod.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Andrew Jeffery <andrew@aj.id.au>,
qemu-arm@nongnu.org, Joel Stanley <joel@jms.id.au>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] MAINTAINERS: Change status to Odd Fixes
Date: Tue, 2 Nov 2021 17:42:16 +0100 [thread overview]
Message-ID: <e60b830f-aaf5-a465-c85f-17aee56bb1d0@kaod.org> (raw)
In-Reply-To: <CAFEAcA__8Rmrie2FSf+WOs987wZf4pa8rC5JXuyMA3WBQVe=Bw@mail.gmail.com>
On 11/2/21 17:18, Peter Maydell wrote:
> On Mon, 1 Nov 2021 at 18:31, Cédric Le Goater <clg@kaod.org> wrote:
>>
>> I haven't done any Aspeed development for a couple of years now and
>> maintaining the Aspeed QEMU machines has been a side project since.
>> I don't have time anymore.
>
> Thanks for the work you've done on this over the years.
>
> I guess this means I should start picking up aspeed-related
> patches into the target-arm queue again ?
Yes. I think that's better. Unless someone volunteers.
> Are there any currently on-list aspeed patches that I
> should put into my to-review queue, or are we up to date
> at the moment?
My last PR for 6.2 should have captured them all.
I kept the FMC WDT2 patches in my aspeed-6.2 branch because I had
information from Aspeed on their logic and my modelling is wrong.
Other patches are not ready for upstream, eMMC for instance.
Thanks,
C.
next prev parent reply other threads:[~2021-11-02 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 18:31 [PATCH] MAINTAINERS: Change status to Odd Fixes Cédric Le Goater
2021-11-02 16:18 ` Peter Maydell
2021-11-02 16:42 ` Cédric Le Goater [this message]
2021-11-02 22:35 ` Andrew Jeffery
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=e60b830f-aaf5-a465-c85f-17aee56bb1d0@kaod.org \
--to=clg@kaod.org \
--cc=andrew@aj.id.au \
--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).