From: Eric Blake <eblake@redhat.com>
To: penghao122@sina.com, qemu-devel <qemu-devel@nongnu.org>
Cc: qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] keyboard: handle ps2 typing buffer overrun
Date: Mon, 18 May 2015 06:56:58 -0600 [thread overview]
Message-ID: <5559E19A.7080604@redhat.com> (raw)
In-Reply-To: <5559E118.9070606@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On 05/18/2015 06:54 AM, Eric Blake wrote:
> On 05/17/2015 10:00 AM, penghao122@sina.com wrote:
>> Subject: [PATCH] keyboard: handle ps2 typing buffer overrun
>
> This line is redundant.
>
> Also, you have tried to send this patch more than once. Please be sure
> to include a proper 'v3' or 'v4' in the subject line, as appropriate.
>
>> Starting a linux guest with ps2 keyboard, if you type many times during leaving
>> grub and into linux kernel,then you can't use keyboard after linux initialization finished.
>> Specally when you setup linux guest from iso file,you will type in grub.
>
> s/Specally/Specifically,/
> s/file,you/file, you/
In fact, I called these out on your v2 submission.
https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg00938.html
Sending a v3 without addressing points made in v2 is not good - it
wastes everyone's time, and makes it more likely that your patch will be
intentionally overlooked.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-05-18 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 16:00 [Qemu-devel] [PATCH] keyboard: handle ps2 typing buffer overrun penghao122
2015-05-18 12:54 ` Eric Blake
2015-05-18 12:56 ` Eric Blake [this message]
2015-06-03 14:16 ` Michael Tokarev
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=5559E19A.7080604@redhat.com \
--to=eblake@redhat.com \
--cc=penghao122@sina.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.