From: "Michael Büsch" <m@bues.ch>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: event subsystem: Define conference event types
Date: Mon, 1 Apr 2013 14:08:56 +0200 [thread overview]
Message-ID: <20130401140856.776f11f7@milhouse> (raw)
[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]
In order to improve the media coverage of important developer
conference events, extend the Linux event subsystem by corresponding
event type numbers.
Instead of referring to events by cryptic acronyms that nobody
knows the real meaning of, use even shorter acronyms defined to
hexadecimal numbers that every real hacker is familiar with.
Signed-off-by: Michael Buesch <m@bues.ch>
---
Index: linux/include/uapi/linux/input.h
===================================================================
--- linux.orig/include/uapi/linux/input.h 2013-02-28 22:27:32.798071135 +0100
+++ linux/include/uapi/linux/input.h 2013-04-01 13:56:05.715754517 +0200
@@ -183,6 +183,7 @@
#define EV_FF 0x15
#define EV_PWR 0x16
#define EV_FF_STATUS 0x17
+#define EV_CONFERENCE 0x18
#define EV_MAX 0x1f
#define EV_CNT (EV_MAX+1)
@@ -750,6 +751,25 @@
#define KEY_CNT (KEY_MAX+1)
/*
+ * Conference events
+ */
+#define CONF_KS 0x00 /* Kernel Summit */
+#define CONF_WNS 0x01 /* Wireless Networking Summit */
+#define CONF_ABS 0x02 /* Android Builders Summit */
+#define CONF_ALS 0x03 /* Automotive Linux Summit */
+#define CONF_LFCS 0x04 /* Linux Foundation Collaboration Summit */
+#define CONF_ELC 0x05 /* Embedded Linux Conference */
+#define CONF_FOSDEM 0x06 /* uhm, ... *scratches head* */
+#define CONF_KLF 0x07 /* Korea Linux Forum */
+#define CONF_LCE 0x08 /* LinuxCon Europe */
+#define CONF_LCA 0x09 /* linux.conf.au */
+#define CONF_LCJ 0x0A /* LinuxCon Japan */
+#define CONF_LCNA 0x0B /* LinuxCon North America */
+#define CONF_LPC 0x0C /* Linux Plumbers Conference */
+#define CONF_LSS 0x0D /* Linux Security Summit */
+#define CONF_PC 0x0E /* PyCon */
+
+/*
* Relative axes
*/
--
Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-04-01 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 12:08 Michael Büsch [this message]
2013-04-01 19:04 ` Greg KH
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=20130401140856.776f11f7@milhouse \
--to=m@bues.ch \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome