From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alexander Graf <agraf@suse.de>, Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 1/1] xhci: generate a Transfer Event for each Transfer TRB with the IOC bit set
Date: Wed, 04 Mar 2015 16:51:10 +0100 [thread overview]
Message-ID: <54F729EE.4030202@redhat.com> (raw)
In-Reply-To: <CAFEAcA_0d81Fr-Xf2KoRXRFCyQWuwX5MXUKCqgM+41nOyWH=Kw@mail.gmail.com>
On 03/04/15 15:10, Peter Maydell wrote:
> On 4 March 2015 at 18:03, Laszlo Ersek <lersek@redhat.com> wrote:
>> Hi Peter,
>>
>> sorry about poking you -- I'm aware you've been on vacation, but in
>> <http://lists.nongnu.org/archive/html/qemu-devel/2015-03/msg00174.html>
>> you said you still inteded to pull stuff.
>>
>> So, can you please pull this? :) I'd like to enable the XHCI driver in
>> both OVMF and AAVMF, and I'd like to reference the qemu commit in the
>> edk2 commit messages.
>
> This pull request is only one day old! Even when I'm at work
> you shouldn't expect a one-day turnaround on pullreqs. (It
> might happen if you get lucky with the timing, but it
> probably won't, especially since I generally process pulls
> first-in-first-out.) A week is probably a more reasonable
> point to prod at.
Apologies then. /me hides
Laszlo
next prev parent reply other threads:[~2015-03-04 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 8:14 [Qemu-devel] [PULL 0/1] xhci: generate a Transfer Event for each Transfer TRB with the IOC bit set Gerd Hoffmann
2015-03-03 8:14 ` [Qemu-devel] [PULL 1/1] " Gerd Hoffmann
2015-03-04 9:03 ` Laszlo Ersek
2015-03-04 11:02 ` Gerd Hoffmann
2015-03-04 14:10 ` Peter Maydell
2015-03-04 15:51 ` Laszlo Ersek [this message]
2015-03-08 8:36 ` [Qemu-devel] [PULL 0/1] " Peter Maydell
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=54F729EE.4030202@redhat.com \
--to=lersek@redhat.com \
--cc=agraf@suse.de \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.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).