From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: rjw@sisk.pl, bzolnier@gmail.com, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: linux-next: Tree for July 30
Date: Thu, 31 Jul 2008 12:13:08 -0700 [thread overview]
Message-ID: <20080731121308.bfbdcd0d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080731145023.ZZRA012@mailhub.coreip.homeip.net>
On Thu, 31 Jul 2008 14:54:52 -0400
Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > IOW, if the change responsible for this makes it to the mainline kernel, it
> > will be considered as a regression.
> >
>
> Like I said, I don't agree.
It really really doesn't matter what the causes are or which piece of
code is at fault or anything else like that.
What _does_ matter is that people's stuff will break. Apparently lots
of people's. That's a problem. A _practical_ problem. Can we
pleeeeeeze be practical and find some way of preventing it?
I assume this is the commit?
commit 03bac96fae0efdb25e2059e5accbe4f3ee6328dd
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: Mon Jun 23 10:47:34 2008 -0400
Input: expand keycode space
Expand the number of potential key codes from 512 to 768 since people
are coming up with more and more keys.
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
diff --git a/include/linux/input.h b/include/linux/input.h
index a5802c9..7fae1de 100644
--- a/include/linux/input.h
+++ b/include/linux/input.h
@@ -579,7 +579,7 @@ struct input_absinfo {
/* We avoid low common keys in module aliases so they don't get huge. */
#define KEY_MIN_INTERESTING KEY_MUTE
-#define KEY_MAX 0x1ff
+#define KEY_MAX 0x2ff
#define KEY_CNT (KEY_MAX+1)
/*
diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
index c4db582..0dddfa4 100644
--- a/include/linux/mod_devicetable.h
+++ b/include/linux/mod_devicetable.h
@@ -274,7 +274,7 @@ struct pcmcia_device_id {
/* Input */
#define INPUT_DEVICE_ID_EV_MAX 0x1f
#define INPUT_DEVICE_ID_KEY_MIN_INTERESTING 0x71
-#define INPUT_DEVICE_ID_KEY_MAX 0x1ff
+#define INPUT_DEVICE_ID_KEY_MAX 0x2ff
#define INPUT_DEVICE_ID_REL_MAX 0x0f
#define INPUT_DEVICE_ID_ABS_MAX 0x3f
#define INPUT_DEVICE_ID_MSC_MAX 0x07
I'm unable to work out how necessary this change is?
Please: what proportion of the existing X installations do you expect will
be affected by this?
next prev parent reply other threads:[~2008-07-31 19:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 7:06 linux-next: Tree for July 30 Stephen Rothwell
2008-07-30 14:47 ` Takashi Iwai
2008-07-31 6:10 ` Andrew Morton
2008-07-31 14:07 ` Dmitry Torokhov
2008-07-31 15:36 ` Bartlomiej Zolnierkiewicz
2008-07-31 15:56 ` Dmitry Torokhov
2008-07-31 17:44 ` Andrew Morton
2008-07-31 18:17 ` Dmitry Torokhov
2008-07-31 18:26 ` Andrew Morton
2008-07-31 18:34 ` Dmitry Torokhov
2008-07-31 18:55 ` Andrew Morton
2008-07-31 19:03 ` Dmitry Torokhov
2008-07-31 19:20 ` Hugh Dickins
2008-07-31 18:48 ` Rafael J. Wysocki
2008-07-31 18:54 ` Dmitry Torokhov
2008-07-31 19:10 ` Linus Torvalds
2008-07-31 19:24 ` Dmitry Torokhov
2008-07-31 19:42 ` Dmitry Torokhov
2008-07-31 20:10 ` Andrew Morton
2008-08-07 18:11 ` Dmitry Torokhov
2008-08-07 18:50 ` Andrew Morton
2008-08-07 19:06 ` Dmitry Torokhov
2008-08-07 18:55 ` Rafael J. Wysocki
2008-08-01 19:12 ` Linus Torvalds
2008-08-01 19:23 ` Dmitry Torokhov
2008-08-01 19:26 ` Linus Torvalds
2008-07-31 19:44 ` Linus Torvalds
2008-07-31 20:05 ` Dmitry Torokhov
2008-07-31 20:16 ` Linus Torvalds
2008-07-31 20:28 ` Linus Torvalds
2008-07-31 20:39 ` Dmitry Torokhov
2008-07-31 20:28 ` Dmitry Torokhov
2008-07-31 19:13 ` Andrew Morton [this message]
2008-07-31 19:57 ` Rafael J. Wysocki
2008-08-04 5:47 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-07-30 8:21 Stephen Rothwell
2010-07-30 5:10 Stephen Rothwell
2012-07-30 4:02 Stephen Rothwell
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=20080731121308.bfbdcd0d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.