From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Cédric Le Goater" <clg@kaod.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Cameron Esfahani via" <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH] hw/arm/aspeed: Map the UART5 device unconditionally
Date: Wed, 30 Sep 2020 14:59:30 +0930 [thread overview]
Message-ID: <fd68ae45-da39-44fe-b07f-2510481dbf7f@www.fastmail.com> (raw)
In-Reply-To: <4648c188-cacc-c532-857c-f0206f60e109@kaod.org>
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 :
> >>
> >> 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!
next prev parent reply other threads:[~2020-09-30 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 21:24 [PATCH] hw/arm/aspeed: Map the UART5 device unconditionally Philippe Mathieu-Daudé
2020-09-06 7:35 ` Cédric Le Goater
2020-09-15 17:23 ` Philippe Mathieu-Daudé
2020-09-16 5:51 ` Cédric Le Goater
2020-09-17 16:57 ` Philippe Mathieu-Daudé
2020-09-17 17:03 ` Cédric Le Goater
2020-09-30 5:29 ` Andrew Jeffery [this message]
2020-09-30 10:07 ` Cédric Le Goater
2020-10-01 0:37 ` 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=fd68ae45-da39-44fe-b07f-2510481dbf7f@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=f4bug@amsat.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).