From: "Michael S. Tsirkin" <mst@redhat.com>
To: Calvin Lee <cyrus296@gmail.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] Ping [PATCH RFC v2 0/2] Fix UART serial implementation
Date: Wed, 23 May 2018 17:51:08 +0300 [thread overview]
Message-ID: <20180523175039-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAG7gSg0DJHjZiPZr6+itsmSOGJ372HRipEUsh2x8dj8EWUjkhg@mail.gmail.com>
On Mon, May 21, 2018 at 10:40:33AM -0600, Calvin Lee wrote:
> Hello,
>
> It's been about a week since the last email to my patches, in case anyone would
> like to review but missed them.
>
> Patches are the following on patchwork:
> http://patchwork.ozlabs.org/patch/912281/
> http://patchwork.ozlabs.org/patch/912282/
>
> And the following on patchew:
> http://patchew.org/QEMU/20180512000545.966-1-cyrus296@gmail.com/
>
> Thank you,
> Calvin Lee
If you'd like these merged, pls re-post without an RFC tag.
--
MST
next prev parent reply other threads:[~2018-05-23 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 16:40 [Qemu-devel] Ping [PATCH RFC v2 0/2] Fix UART serial implementation Calvin Lee
2018-05-23 14:51 ` Michael S. Tsirkin [this message]
2018-05-23 14:52 ` Michael S. Tsirkin
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=20180523175039-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cyrus296@gmail.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--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).