From: Marvin Raaijmakers <marvin.nospam@gmail.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
federico ferri <xaero@inwind.it>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@atrey.karlin.mff.cuni.cz, mzxrlshmm@0pointer.de
Subject: Re: [PATCH] input: change SysRq keycode for systems without SysRq key
Date: Fri, 17 Aug 2007 17:01:52 +0200 [thread overview]
Message-ID: <1187362912.3684.33.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0708171638560.2460@twin.jikos.cz>
Ah this is the part that checks for a change in key state:
!!test_bit(usage->code, input->key) != value
Well, in that case: yes, this is the functionality I was looking for.
- Marvin
On Fri, 2007-08-17 at 16:42 +0200, Jiri Kosina wrote:
> On Fri, 17 Aug 2007, Marvin Raaijmakers wrote:
>
> > This code doesn't filter out the "status events" right? So that still
> > needs to be done(?).
>
> Hi Marvin,
>
> I am not sure what you mean by that -- this patch is supposed to issue
> input_event(EV_MSC, MSC_SCAN) if and only if it would mean the change in
> key state.
>
prev parent reply other threads:[~2007-08-17 15:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 17:04 [PATCH] input: change SysRq keycode for systems without SysRq key federico ferri
2007-07-15 18:03 ` Linus Torvalds
2007-07-15 18:34 ` federico ferri
2007-07-15 18:57 ` Linus Torvalds
2007-07-15 22:04 ` federico ferri
2007-07-15 22:15 ` Linus Torvalds
2007-07-16 12:41 ` Dmitry Torokhov
2007-07-17 6:40 ` federico ferri
2007-07-17 15:11 ` Dmitry Torokhov
2007-07-18 20:55 ` federico ferri
2007-07-19 21:00 ` Dmitry Torokhov
2007-07-19 21:00 ` Dmitry Torokhov
2007-07-19 21:39 ` federico ferri
2007-07-19 22:32 ` Dmitry Torokhov
2007-07-19 23:29 ` federico ferri
2007-07-30 14:09 ` Jiri Kosina
2007-08-02 21:27 ` Vojtech Pavlik
2007-08-17 8:25 ` Marvin Raaijmakers
2007-08-17 10:22 ` Jiri Kosina
2007-08-17 14:35 ` Marvin Raaijmakers
2007-08-17 14:42 ` Jiri Kosina
2007-08-17 15:01 ` Marvin Raaijmakers [this message]
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=1187362912.3684.33.camel@localhost.localdomain \
--to=marvin.nospam@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@jikos.cz \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=mzxrlshmm@0pointer.de \
--cc=vojtech@suse.cz \
--cc=xaero@inwind.it \
/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).