mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Keng-Yü Lin" <keng-yu.lin@canonical.com>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [stable] [2.6.31.stable] Input: atkbd - add force relese key  quirk for Samsung R59P/R60P/R61P
Date: Mon, 21 Dec 2009 12:59:43 +0800	[thread overview]
Message-ID: <d8fcdb790912202059v5e04b8a2j4fc10324c3c80fa9@mail.gmail.com> (raw)
In-Reply-To: <20091216191938.GB16321@kroah.com>

Dear Greg:
  This patch is not upstream. Since 2.6.32, there is an interface in
/sys for handling the force_release events from userspace, so such
quirk patches are no longer accepted upstream now. But this patch is
valid for version 2.6.31 downwards.

  Regards,

-Keng-Yu

2009/12/17 Greg KH <greg@kroah.com>:
> I don't see the git commit id for the patch below, which is needed if it
> is to be accepted into the -stable kernel tree.
>
> Do you have it?
>
> thanks,
>
> greg k-h
>
> On Mon, Dec 07, 2009 at 05:26:54PM +0800, Keng-Yu Lin wrote:
>> OriginalAuthor:
>>     Moiseev Vladimir <cdb@linkycat.com>
>>     Alexander Huhlaev <sancheolz@gmail.com>
>>
>> BugLink: http://bugs.launchpad.net/bugs/253874
>>
>> Signed-off-by: Keng-Yu Lin <keng-yu.lin@canonical.com>
>> ---
>>  drivers/input/keyboard/atkbd.c |    9 +++++++++
>>  1 files changed, 9 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
>> index 6c6a09b..abc314f 100644
>> --- a/drivers/input/keyboard/atkbd.c
>> +++ b/drivers/input/keyboard/atkbd.c
>> @@ -1608,6 +1608,15 @@ static struct dmi_system_id atkbd_dmi_quirk_table[] __initdata = {
>>               .driver_data = atkbd_samsung_forced_release_keys,
>>       },
>>       {
>> +             .ident = "Samsung R59P/R60P/R61P",
>> +             .matches = {
>> +                     DMI_MATCH(DMI_SYS_VENDOR, "SAMSUNG ELECTRONICS CO., LTD."),
>> +                     DMI_MATCH(DMI_PRODUCT_NAME, "R59P/R60P/R61P"),
>> +             },
>> +             .callback = atkbd_setup_forced_release,
>> +             .driver_data = atkbd_samsung_forced_release_keys,
>> +     },
>> +     {
>>               .ident = "Fujitsu Amilo PA 1510",
>>               .matches = {
>>                       DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU SIEMENS"),
>> --
>> 1.6.3.3
>>
>> _______________________________________________
>> stable mailing list
>> stable@linux.kernel.org
>> http://linux.kernel.org/mailman/listinfo/stable
>

  reply	other threads:[~2009-12-21  4:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  9:26 Keng-Yu Lin
2009-12-16 19:19 ` [stable] " Greg KH
2009-12-21  4:59   ` Keng-Yü Lin [this message]
2010-01-05 19:29     ` Greg KH

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=d8fcdb790912202059v5e04b8a2j4fc10324c3c80fa9@mail.gmail.com \
    --to=keng-yu.lin@canonical.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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

all inboxes | Powered by JetHome®