Hi
On Wed, Nov 12, 2014 at 1:41 PM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Wed, Nov 12, 2014 at 8:40 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi David,
On Tue, Nov 04, 2014 at 06:12:23PM +0100, David Herrmann wrote:
+static int bits_from_user(unsigned long *bits,
Hi
On Wed, Nov 12, 2014 at 8:40 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi David,
On Tue, Nov 04, 2014 at 06:12:23PM +0100, David Herrmann wrote:
+static int bits_from_user(unsigned long *bits, unsigned int maxbit,
+ unsigned int maxlen, const void __user
Hi David,
On Tue, Nov 04, 2014 at 06:12:23PM +0100, David Herrmann wrote:
+static int bits_from_user(unsigned long *bits, unsigned int maxbit,
+ unsigned int maxlen, const void __user *p, int compat)
+{
+ int len;
+
+#if IS_ENABLED(CONFIG_COMPAT)
+ if (compat)
Hardware manufacturers group keys in the weirdest way possible. This may
cause a power-key to be grouped together with normal keyboard keys and
thus be reported on the same kernel interface.
However, user-space is often only interested in specific sets of events.
For instance, daemons dealing
Hi Dmitry
On Wed, Jun 18, 2014 at 7:42 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hardware manufacturers group keys in the weirdest way possible. This may
cause a power-key to be grouped together with normal keyboard keys and
thus be reported on the same kernel interface.
However,
