linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>,
	"Darren Hart" <dvhart@infradead.org>
Cc: arvidjaar@gmail.com, rjw@rjwysocki.net, Jared_Dominguez@dell.com,
	platform-driver-x86@vger.kernel.org, alex.hung@canonical.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] dell-rbtn: Ignore ACPI notifications if device is suspended
Date: Wed, 25 May 2016 22:47:03 +0200	[thread overview]
Message-ID: <57b87380-6ea8-cdaf-b95c-4685fc2a85d1@gmail.com> (raw)
In-Reply-To: <201605252236.55715@pali>

On 25/05/2016 22:36, Pali Rohár wrote:
> On Wednesday 25 May 2016 22:28:47 Darren Hart wrote:
>> On Tue, May 24, 2016 at 10:53:08PM +0200, Gabriele Mazzotta wrote:
>>> Some BIOSes unconditionally send an ACPI notification to RBTN when
>>> the system is resuming from suspend. This makes dell-rbtn send an
>>> input event to userspace as if a function key was pressed. Prevent
>>> this by ignoring all the notifications received while the device
>>> is suspended.
>>>
>>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=106031
>>> Signed-off-by: Gabriele Mazzotta <gabriele.mzt@gmail.com>
>>
>> Gabriele, please include all the maintainers on Cc (Pali was
>> missing).
> 
> Hehe, currently I started git send-email with my changes for v4 :D
> So doing CTRL+C in terminal...
> 
>> Pali, can I have your Reviewed-by?
> 
> Yes as my patch differs only in two words (in comments) :-)
> 
> Anyway, there is missing Andrei's tested-by (from v2 version).

Sorry, I think this was not the first time I excluded Pali's address...

Anyway, there's also Alex's tested-by from v2, which is basically
the same as v4.

> Maybe also this should go to stable tree?
> 

  reply	other threads:[~2016-05-25 20:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 23:49 [PATCH v2] dell-rbtn: Ignore ACPI notifications if device is suspended Gabriele Mazzotta
2016-03-14  7:55 ` Alex Hung
2016-03-14 11:34 ` Gabriele Mazzotta
2016-03-14 11:45   ` Pali Rohár
2016-03-14 12:15     ` Andrei Borzenkov
2016-03-18 15:57     ` Andrei Borzenkov
2016-04-18 12:31       ` Pali Rohár
2016-03-18 22:44 ` [PATCH v3] " Gabriele Mazzotta
2016-03-21 12:17   ` Pali Rohár
2016-03-21 15:13     ` Gabriele Mazzotta
2016-03-24  9:39       ` Pali Rohár
2016-03-24 11:24         ` Gabriele Mazzotta
2016-03-28 17:33           ` Darren Hart
2016-03-28 17:58             ` Gabriele Mazzotta
2016-03-28 18:56               ` Darren Hart
2016-03-28 19:41                 ` Gabriele Mazzotta
2016-03-29  5:24                   ` Darren Hart
2016-03-29 11:13                     ` Gabriele Mazzotta
2016-03-29 13:11             ` Rafael J. Wysocki
2016-04-18 12:35               ` Pali Rohár
2016-04-25 20:06                 ` Gabriele Mazzotta
2016-05-19 13:30                   ` Pali Rohár
2016-05-19 20:18                     ` Darren Hart
2016-05-23 21:26                     ` Darren Hart
2016-05-23 22:06                       ` Pali Rohár
2016-05-23 22:17                         ` Darren Hart
2016-05-23 22:22                           ` Pali Rohár
2016-05-23 23:03                             ` Gabriele Mazzotta
2016-05-24  3:48                               ` Andrei Borzenkov
2016-05-24  7:09                                 ` Pali Rohár
2016-05-24 19:57                                   ` Darren Hart
2016-05-24 20:53                                     ` [PATCH v4] " Gabriele Mazzotta
2016-05-25 20:28                                       ` Darren Hart
2016-05-25 20:36                                         ` Pali Rohár
2016-05-25 20:47                                           ` Gabriele Mazzotta [this message]
2016-05-25 21:20                                             ` Darren Hart

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=57b87380-6ea8-cdaf-b95c-4685fc2a85d1@gmail.com \
    --to=gabriele.mzt@gmail.com \
    --cc=Jared_Dominguez@dell.com \
    --cc=alex.hung@canonical.com \
    --cc=arvidjaar@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).