From: malc <av1474@comtv.ru>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH][RFC] Fix SDL on evdev hosts
Date: Sat, 28 Feb 2009 00:53:35 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.64.0902280053190.5058@linmac.oyster.ru> (raw)
In-Reply-To: <f43fc5580902271210x2ccd7508h6e5e79613c7d50d6@mail.gmail.com>
On Fri, 27 Feb 2009, Blue Swirl wrote:
> On 2/27/09, Anthony Liguori <aliguori@us.ibm.com> wrote:
> > This patch corrects SDL support on X11 hosts using evdev. It's losely based
> > on the previous patch by Dustin Kirkland and the evdev support code in gtk-vnc
> > written by Daniel Berrange.
> >
> > I've tried to take into account all past feedback from previous patches posted
> > including a proper set of configure checks. I've tested this on win32 but
> > I'd like some more eyes to look at it.
> >
> > Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>
> Just a micro nitpick:
> > +#ifndef _QEMU_X_KEYMAP_H
> > +#define _QEMU_X_KEYMAP_H
And it should be QEMU_X_KEYMAP_H.
> > +
> > +extern uint8_t translate_xfree86_keycode(const int key);
> > +
> > +extern uint8_t translate_evdev_keycode(const int key);
> > +
> > +#endif
> > +
>
> Looks like an extra newline at the end of file? ;-)
>
> The #endif does not have the traditional /* _QEMU_X_KEYMAP_H */
> ending, but I don't care much for those.
>
>
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-02-27 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 17:34 [Qemu-devel] [PATCH][RFC] Fix SDL on evdev hosts Anthony Liguori
2009-02-27 20:10 ` Blue Swirl
2009-02-27 20:11 ` Anthony Liguori
2009-02-27 21:53 ` malc [this message]
2009-03-09 22:53 ` malc
2009-03-10 1:51 ` Anthony Liguori
2009-03-10 19:16 ` malc
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=Pine.LNX.4.64.0902280053190.5058@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=aliguori@us.ibm.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).