From: akpm@linux-foundation.org
To: mjg59@srcf.ucam.org, dtor@mail.ru, kristen.c.accardi@intel.com,
lenb@kernel.org, mjg@redhat.com, mm-commits@vger.kernel.org
Subject: - input-add-switch-for-dock-events.patch removed from -mm tree
Date: Mon, 21 Jul 2008 14:34:07 -0700 [thread overview]
Message-ID: <200807212134.m6LLY7Zh025645@imap1.linux-foundation.org> (raw)
The patch titled
input: add switch for dock events
has been removed from the -mm tree. Its filename was
input-add-switch-for-dock-events.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: input: add switch for dock events
From: Matthew Garrett <mjg59@srcf.ucam.org>
Add a SW_DOCK switch to input.h. ACPI docks currently send their docking
status as a uevent, but not all docks are ACPI or correspond to a device.
In that case, it makes more sense to simply generate an input event on
docking or undocking.
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Cc: Dmitry Torokhov <dtor@mail.ru>
Cc: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: Len Brown <lenb@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/input.h | 1 +
1 file changed, 1 insertion(+)
diff -puN include/linux/input.h~input-add-switch-for-dock-events include/linux/input.h
--- a/include/linux/input.h~input-add-switch-for-dock-events
+++ a/include/linux/input.h
@@ -642,6 +642,7 @@ struct input_absinfo {
#define SW_RFKILL_ALL 0x03 /* rfkill master switch, type "any"
set = radio enabled */
#define SW_RADIO SW_RFKILL_ALL /* deprecated */
+#define SW_DOCK 0x04 /* set = plugged into dock */
#define SW_MAX 0x0f
#define SW_CNT (SW_MAX+1)
_
Patches currently in -mm which might be from mjg59@srcf.ucam.org are
origin.patch
misc-add-hp-wmi-laptop-extras-driver.patch
reply other threads:[~2008-07-21 21:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200807212134.m6LLY7Zh025645@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dtor@mail.ru \
--cc=kristen.c.accardi@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=mjg@redhat.com \
--cc=mm-commits@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