qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Vesely <jano.vesely@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 2/3] usb-hid: Add high speed mouse configuration
Date: Fri, 26 Sep 2014 10:43:13 -0400	[thread overview]
Message-ID: <1411742593.21562.2.camel@gmail.com> (raw)
In-Reply-To: <1411715162.865.4.camel@nilsson.home.kraxel.org>

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

On Fri, 2014-09-26 at 09:06 +0200, Gerd Hoffmann wrote:
> On Do, 2014-09-25 at 17:38 -0400, Jan Vesely wrote:
> > v2: add usb_mouse_properties
> >     use macros for bmAttributes
> > v3: rebase
> > v4: rebase
> 
> patch looks good, the only thing missing is the compat property, to make
> sure qemu machine types for 2.1 & older continue to have usb1 mouse+kbd
> by default.
> 
> The property for the tablet is in hw/i386/pc_piix.c, have a look there
> how to do it.  The compat properties for more recent machine types live
> in a header file (include/hw/i386/pc.h) so they can be shared between pc
> and q35.


I gave mouse and kbd the same treatment as tablet has in
hw/i386/pc_piix.c.
Speaking about properties do I need to add something for display and
head properties?
tablet adds both of them and they seem to be used together, however
keyboard only had display, and I added neither for mouse.


> 
> Oh, and the patch history should not be in the commit message.  You can
> add the history as notes (see 'git notes').  'git format-patch' will use
> three dashes to separate the notes and 'git am' will strip them off so
> they appear on the list message but not in the commit log.  Adding the
> tree dashes separator to the commit message will work too, at least as
> long as you don't send pull requests (in which case 'git am' would have
> no chance to strip off the notes).

OK I'll move these out of commit messages.

thanks,
jan

> 
> cheers,
>   Gerd
> 
> 



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-09-26 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 21:38 [Qemu-devel] [PATCH v2 1/3] usb-hid: Move descriptor decision to usb-hid initfn Jan Vesely
2014-09-25 21:38 ` [Qemu-devel] [PATCH v4 2/3] usb-hid: Add high speed mouse configuration Jan Vesely
2014-09-26  7:06   ` Gerd Hoffmann
2014-09-26 14:43     ` Jan Vesely [this message]
2014-09-29  7:32       ` Gerd Hoffmann
2014-09-25 21:38 ` [Qemu-devel] [PATCH v2 3/3] usb-hid: Add high speed keyboard configuration Jan Vesely
2014-09-26  6:21 ` [Qemu-devel] [PATCH v2 1/3] usb-hid: Move descriptor decision to usb-hid initfn Gonglei (Arei)
2014-09-26  6:53   ` Gerd Hoffmann
2014-09-26  7:11     ` Gonglei (Arei)
  -- strict thread matches above, loose matches on Subject: below --
2014-09-30  2:21 [Qemu-devel] [PATCH v3 " Jan Vesely
2014-09-30  2:21 ` [Qemu-devel] [PATCH v4 2/3] usb-hid: Add high speed mouse configuration Jan Vesely

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=1411742593.21562.2.camel@gmail.com \
    --to=jano.vesely@gmail.com \
    --cc=kraxel@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).