All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Darren Hart <dvhart@infradead.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	Gabriele Mazzotta <gabriele.mzt@gmail.com>,
	mjg59@srcf.ucam.org, platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] dell-wmi: Don't send unneeded keypresses
Date: Sat, 20 Dec 2014 10:10:17 +0100	[thread overview]
Message-ID: <201412201010.18151@pali> (raw)
In-Reply-To: <20141203180329.GB20370@vmdeb7>

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

On Wednesday 03 December 2014 19:03:37 Darren Hart wrote:
> On Fri, Dec 05, 2014 at 10:07:35PM +0100, Pali Rohár wrote:
> > On Friday 05 December 2014 21:41:22 Pavel Machek wrote:
> > > On Fri 2014-12-05 21:31:34, Pali Rohár wrote:
> > > > On Wednesday 03 December 2014 14:34:32 Darren Hart wrote:
> > > > > On Thu, Dec 04, 2014 at 12:16:20AM +0100, Gabriele
> > > > > Mazzotta
> > > > 
> > > > wrote:
> > > > > > Currently dell-wmi reports keypresses for WMI events
> > > > > > that are notifications of changes performed by the
> > > > > > BIOS. This patch series make sure that no keypresses
> > > > > > are sent for those events so that nothing is done
> > > > > > from userspace.
> > > > > > 
> > > > > > Gabriele Mazzotta (3):
> > > > > >   dell-wmi: Use appropriate keycode for radio state
> > > > > >   changes dell-wmi: Don't report keypresses for
> > > > > >   radio state changes
> > > > > 
> > > > > Merged into one patch, queued.
> > > > > 
> > > > > >   dell-wmi: Don't report keypresses on keybord
> > > > > >   illumination change
> > > > > 
> > > > > Queued.
> > > > > 
> > > > > Thanks Gabriele.
> > > > 
> > > > Darren, what do you think about sending patch into
> > > > stable kernel?
> > > 
> > > I'd suggest against that. -stable is for "serious" bugs,
> > > and we don't want to change this kind of behaviour in
> > > -stable kernel.
> > > 
> > > 								Pavel
> > 
> > Ok, I agree that it is subjective how serious it is...
> > Just to remind that patch fixing problem described in
> > 
> > http://www.spinics.net/lists/platform-driver-x86/msg05922.ht
> > ml
> > http://www.spinics.net/lists/platform-driver-x86/msg05924.h
> > tml
> 
> I don't have any objection to sending this back to stable.
> Stable is for fixing REAL bugs, as opposed to theorhetical
> races, etc. This is a "real" bug.
> 
> As to not chaning behavior, if it's OK for mainline, it's OK
> for stable. At least that is my understanding of it. Folks
> are free to verify with Greg if they disagree.

Darren, so how you decided? Now when patches are in linus tree, 
are you going to send them to stable tree?

-- 
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:[~2014-12-20  9:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 23:16 [PATCH 0/3] dell-wmi: Don't send unneeded keypresses Gabriele Mazzotta
2014-12-03 13:34 ` Darren Hart
2014-12-05 20:31   ` Pali Rohár
2014-12-05 20:41     ` Pavel Machek
2014-12-05 21:07       ` Pali Rohár
2014-12-03 18:03         ` Darren Hart
2014-12-20  9:10           ` Pali Rohár [this message]
2014-12-20 15:11             ` Pavel Machek
2014-12-20 16:16               ` Darren Hart
2014-12-20 17:03                 ` Gabriele Mazzotta
2014-12-20 20:18                   ` Darren Hart
2014-12-20 16:28               ` Henrique de Moraes Holschuh
2014-12-20 16:58                 ` Darren Hart
     [not found]                 ` <CAHYPw2FVniWP-7e3K905Xd5yh2zK-ytTD0z3CwwqZFTqMX5kXA@mail.gmail.com>
2014-12-20 18:55                   ` Pavel Machek
2014-12-03 23:16 ` [PATCH 1/3] dell-wmi: Use appropriate keycode for radio state changes Gabriele Mazzotta
2014-12-03 23:16 ` [PATCH 2/3] dell-wmi: Don't report keypresses " Gabriele Mazzotta
2014-12-03 23:16 ` [PATCH 3/3] dell-wmi: Don't report keypresses on keybord illumination change Gabriele Mazzotta
2014-12-03 23:31   ` 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=201412201010.18151@pali \
    --to=pali.rohar@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=gabriele.mzt@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@ucw.cz \
    --cc=platform-driver-x86@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.