From: Miika S <miika9764@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] input: add missing JIS keys to virtio input
Date: Sat, 23 Dec 2017 11:58:10 +0200 [thread overview]
Message-ID: <CABMrAh+327uiN0HBf_U-FquDxZRGAng_1bstadoO8pda-Xa5SA@mail.gmail.com> (raw)
In-Reply-To: <7579578e-2e0f-a6bb-f5be-ae7dfbafd6c4@redhat.com>
Thank you for pointing out these errors. I've sent a new set
of patches with the errors addressed, but later noticed that
the new revision should have been titled [PATCH v2]. So to
anybody reading this thread, it has been replaced with a new
one.
On Thu, Dec 21, 2017 at 12:35 AM, Eric Blake <eblake@redhat.com> wrote:
> On 12/18/2017 07:24 AM, Miika S wrote:
>>
>> Signed-off-by: Miika S <miika9764@gmail.com>
>> ---
>> hw/input/virtio-input-hid.c | 7 +++++++
>> qapi/ui.json | 2 +-
>> ui/keycodemapdb | 2 +-
>> 3 files changed, 9 insertions(+), 2 deletions(-)
>
>
> When sending a multi-patch series, please remember to include the 0/3 cover
> letter. 'git config format.coverletter auto' can make this task easier to
> remember.
>
>
>> static const unsigned int keymap_button[INPUT_BUTTON__MAX] = {
>> diff --git a/qapi/ui.json b/qapi/ui.json
>> index 07b468f625..da4be505ac 100644
>> --- a/qapi/ui.json
>> +++ b/qapi/ui.json
>> @@ -775,7 +775,7 @@
>> 'left', 'up', 'down', 'right', 'insert', 'delete', 'stop',
>> 'again',
>> 'props', 'undo', 'front', 'copy', 'open', 'paste', 'find',
>> 'cut',
>> 'lf', 'help', 'meta_l', 'meta_r', 'compose', 'pause',
>> - 'ro', 'hiragana', 'henkan', 'yen',
>> + 'ro', 'hiragana', 'muhenkan', 'henkan', 'katakanahiragana',
>> 'yen',
>> 'kp_comma', 'kp_equals', 'power', 'sleep', 'wake',
>> 'audionext', 'audioprev', 'audiostop', 'audioplay',
>> 'audiomute',
>> 'volumeup', 'volumedown', 'mediaselect',
>
>
> Missing documentation that calls out which enum values were added in 2.12.
>
>> diff --git a/ui/keycodemapdb b/ui/keycodemapdb
>> index 10739aa260..05dad417e9 160000
>> --- a/ui/keycodemapdb
>> +++ b/ui/keycodemapdb
>> @@ -1 +1 @@
>> -Subproject commit 10739aa26051a5d49d88132604539d3ed085e72e
>> +Subproject commit 05dad417e9d0b37ee1fba33056d91a6b734b3357
>
>
> Generally, the commit message body should call out that a submodule change
> alongside other changes is intentional.
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3266
> Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2017-12-23 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 13:24 [Qemu-devel] [PATCH 1/3] input: add missing JIS keys to virtio input Miika S
2017-12-18 13:24 ` [Qemu-devel] [PATCH 2/3] input: add mouse side buttons " Miika S
2017-12-18 13:24 ` [Qemu-devel] [PATCH 3/3] input: virtio: don't send mouse wheel event twice Miika S
2017-12-20 22:35 ` [Qemu-devel] [PATCH 1/3] input: add missing JIS keys to virtio input Eric Blake
2017-12-23 9:58 ` Miika S [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-22 15:25 [Qemu-devel] [PATCH 0/3] input: add keys and mouse buttons " Miika S
2017-12-22 15:25 ` [Qemu-devel] [PATCH 1/3] input: add missing JIS keys " Miika S
2018-01-15 10:40 ` Daniel P. Berrange
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=CABMrAh+327uiN0HBf_U-FquDxZRGAng_1bstadoO8pda-Xa5SA@mail.gmail.com \
--to=miika9764@gmail.com \
--cc=eblake@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).