From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 1/4] adb-keys.h: initial commit
Date: Sat, 5 Mar 2016 17:02:20 -0700 [thread overview]
Message-ID: <56DB738C.3040204@redhat.com> (raw)
In-Reply-To: <065EA09A-157B-4F3A-BEFC-7C71F8020DC9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3129 bytes --]
On 03/04/2016 10:15 PM, Programmingkid wrote:
> This commit implements the adb-keys.h file. It holds information on adb keycode
> values.
>
> Signed-off-by: John Arbuckle <programmingkidx@gmail.com>
> ---
> Changed name of file from MacKeys.h to adb-keys.h.
> Changed name of constants from MAC_KEYS_ to ADB_KEYS_.
>
> include/hw/input/adb-keys.h | 160 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 160 insertions(+)
> create mode 100644 include/hw/input/adb-keys.h
Thanks; you're getting closer at decent submission style. Your
threading is still broken, though (the mail is missing an 'In-Reply-To:'
header that refers to <F4F7A35F-2C22-4F54-821F-03DDE2B146BC@gmail.com>
from the 0/4 cover letter); you can see this in the list archives:
https://lists.gnu.org/archive/html/qemu-devel/2016-03/threads.html#01180
Note how your messages each appear as top-level threads, while most
other series are properly threaded.
>
> diff --git a/include/hw/input/adb-keys.h b/include/hw/input/adb-keys.h
> new file mode 100644
> index 0000000..6e009ee
> --- /dev/null
> +++ b/include/hw/input/adb-keys.h
> @@ -0,0 +1,160 @@
> +/*
> + * QEMU System Emulator
> + *
> + * Copyright (c) 2003-2008 Fabrice Bellard
Fabrice did not write this file. You're probably better off replacing
this line wholesale with a Copyright 2016 and claiming copyright
yourself, since it is new material from you that is not substantially
copied from some existing file.
> + *
> + * Permission is hereby granted, free of charge, to any person obtaining a copy
> + * of this software and associated documentation files (the "Software"), to deal
> + * in the Software without restriction, including without limitation the rights
> + * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
> + * copies of the Software, and to permit persons to whom the Software is
> + * furnished to do so, subject to the following conditions:
Any reason you chose the weaker BSD license instead of the
project-default of GPLv2+?
> +/*
> + * adb-keys.h
> + *
> + * Provides a enum of all the Macintosh keycodes.
s/a enum/an enum/
Can you provide a URL to the source document that you used for coming up
with this list, so that we can better double-check your work? (Do it as
a comment in this file, if you have one)
> + * Note: keys like Power, volume related, and eject are handled at a lower
> + * level and are not available to QEMU. That doesn't mean we can't
> + * substitute one key for another. The function keys like F1 make a good
> + * substitute for these keys. This can be done in the GTK, SDL, or Cocoa
> + * code.
> + */
> +
> +#ifndef __ADBKEYS__
> +#define __ADBKEYS__
The name '__ADBKEYS__' is reserved for the compiler's use; you risk a
future collision for no good reason. It's fine to use 'ADB_KEYS_H' as
your witness, better matching your filename and staying out of reserved
namespace.
--
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:[~2016-03-06 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 5:15 [Qemu-devel] [PATCH v3 1/4] adb-keys.h: initial commit Programmingkid
2016-03-06 0:02 ` Eric Blake [this message]
2016-03-06 0:06 ` Programmingkid
2016-03-06 20:35 ` Programmingkid
2016-03-07 21:10 ` Eric Blake
2016-03-07 21:33 ` Programmingkid
2016-03-07 21:44 ` Eric Blake
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=56DB738C.3040204@redhat.com \
--to=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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).