linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyungmin Park <kmpark@infradead.org>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	dmitry.torokhov@gmail.com
Subject: Re: [PATCH] Input notifier support
Date: Fri, 27 Feb 2009 11:11:27 +0900	[thread overview]
Message-ID: <9c9fda240902261811g49483f9fk9ac7945834b8764@mail.gmail.com> (raw)
In-Reply-To: <5d5443650902252301l19d08e67t54c1cea004442be2@mail.gmail.com>

Hi,

On Thu, Feb 26, 2009 at 4:01 PM, Trilok Soni <soni.trilok@gmail.com> wrote:
> Hi Kyungmin,
>
>> diff --git a/drivers/input/input.c b/drivers/input/input.c
>> index 1730d73..7e96635 100644
>> --- a/drivers/input/input.c
>> +++ b/drivers/input/input.c
>> @@ -274,6 +274,8 @@ void input_event(struct input_dev *dev,
>>                add_input_randomness(type, code, value);
>>                input_handle_event(dev, type, code, value);
>>                spin_unlock_irqrestore(&dev->event_lock, flags);
>> +               if (type == EV_KEY)
>> +                       input_notifier_call_chain(value, &code);
>
> This check will be done for every input_report_xxx calls, even for
> touchscreen events (in which case of course it will fail), and I don't
> think this is optimal solution. Users should be given an option to
> disable this if they don't need this notification mechanism.
>
> How about moving this to input_report_key?

Good, Thank you for point it. I will move it to input_report_key.

Thank you,
Kyungmin Park

  reply	other threads:[~2009-02-27  2:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  4:47 [PATCH] Input notifier support Kyungmin Park
2009-02-25  8:03 ` Trilok Soni
2009-02-25  9:55   ` Kyungmin Park
2009-02-26  7:01 ` Trilok Soni
2009-02-27  2:11   ` Kyungmin Park [this message]
2009-02-27 12:35     ` Trilok Soni
2009-02-28 22:30 ` Dmitry Torokhov
2009-02-28 23:34 ` Andi Kleen
2009-03-01  0:42   ` Dmitry Torokhov
2009-03-01  2:52     ` Kyungmin Park
2009-03-01  3:07       ` Dmitry Torokhov
2009-03-01  3:16         ` Kyungmin Park
2009-03-01  6:29           ` Dmitry Torokhov

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=9c9fda240902261811g49483f9fk9ac7945834b8764@mail.gmail.com \
    --to=kmpark@infradead.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soni.trilok@gmail.com \
    /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).