linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: atkbd: Fix release quirk for Dell models
Date: Sun, 5 Apr 2015 00:48:44 +0200	[thread overview]
Message-ID: <201504050048.44878@pali> (raw)
In-Reply-To: <1427639779-27377-1-git-send-email-pali.rohar@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 887 bytes --]

On Sunday 29 March 2015 16:36:19 Pali Rohár wrote:
> This patch fixes commit 61579ba83934 ("Input: atkbd - expand
> Latitude's force release quirk to other Dells"). Before that
> commit release quirks were called for all Dell Latitude
> models. After that commit only for Portable Dell devices. But
> lot of Latitude models are Laptop or Notebook DMI devices so
> quirks are not called.
> 
> Release quirks are still needed also for new Dell Latitude
> models, so this patch enables quirks for all Portable,
> Laptop, Notebook and Sub-Notebook Dell devices.
> 
> Signed-off-by: Pali Rohár <pali.rohar@gmail.com>

Dmitry, Matthew: Can be this patch pushed to 4.0 and backported 
to stable releases? It fix regression caused by specified commit. 
I tested this patch on Latitude E6440 and now all keys are 
correctly released.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-04-04 22:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-29 14:36 [PATCH] Input: atkbd: Fix release quirk for Dell models Pali Rohár
2015-04-04 22:48 ` Pali Rohár [this message]
2015-04-05 21:48 ` Dmitry Torokhov
2015-04-05 22:00   ` Pali Rohár
2015-04-05 23:53     ` Dmitry Torokhov
2015-04-06  8:06       ` Pali Rohár
2015-04-06 16:20         ` Dmitry Torokhov
2015-04-08 20:54           ` Pali Rohár
2015-04-09 16:57             ` Dmitry Torokhov
2015-04-09 17:00               ` Pali Rohár

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=201504050048.44878@pali \
    --to=pali.rohar@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).