From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] platform/x86: peaq-wmi: Add DMI check before binding to the WMI interface
Date: Thu, 5 Oct 2017 20:04:19 +0200 [thread overview]
Message-ID: <ef9ba92b-df20-301e-e63d-6605de0246a6@redhat.com> (raw)
In-Reply-To: <CAHp75VcPvwusgznA_rx7+1bdqjHSJ-Z8CE36EktpegMBoWWCzg@mail.gmail.com>
Hi,
On 05-10-17 19:59, Andy Shevchenko wrote:
> On Thu, Oct 5, 2017 at 5:27 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Hi,
>>
>> On 05-10-17 16:23, Andy Shevchenko wrote:
>>>
>>> On Thu, Oct 5, 2017 at 5:20 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>>>>
>>>> It seems that the WMI GUID used by the PEAQ 2-in-1 WMI hotkeys is not
>>>> as unique as a GUID should be and is used on some other devices too.
>>>>
>>>> This is causing spurious key-press reports on these other devices.
>>>>
>>>> This commits adds a DMI check to the PEAQ 2-in-1 WMI hotkeys driver to
>>>> ensure that it is actually running on a PEAQ 2-in-1, fixing the
>>>> spurious key-presses on these other devices.
>>>>
>>>
>>> Recently I have pushed similar patch (another device). Can you rebase
>>> against testing?
>>
>>
>> That patch adds a blacklist, for yet another model then the 2 bugreports:
>>
>>>> BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1497861
>>>> BugLink: https://bugzilla.suse.com/attachment.cgi?id=743182
>>
>>
>> which I've received. My patch adds a whitelist instead as it seems the GUID
>> used is some very generic GUID,
>
> Since you are maintainer and moreover have a hardware to test I assume
> that's correct thing to do...
>
>> so the blacklist patch should simply be
>> dropped,
>
> ... however, the patch can't be dropped.
>
> Either me, or you in v2 need to revert it. Tell me what you prefer here.
Isn't the whole purpose of having a testing branch that patches can
actually be dropped. AFAIK this has not even hit -next yet, so IMHO
it should just be dropped ?
If it really should be reverted instead I'll leave doing a revert up
to you.
> In any case, please (re)send with Cc to Kai so he or bug reportes may
> have a chance to test it as well.
Ok, done.
Regards,
Hans
next prev parent reply other threads:[~2017-10-05 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 14:20 [PATCH] platform/x86: peaq-wmi: Add DMI check before binding to the WMI interface Hans de Goede
2017-10-05 14:23 ` Andy Shevchenko
2017-10-05 14:27 ` Hans de Goede
2017-10-05 17:59 ` Andy Shevchenko
2017-10-05 18:04 ` Hans de Goede [this message]
2017-10-05 18:12 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2017-10-05 18:04 [PATCH resend] " Hans de Goede
2017-10-05 18:04 ` [PATCH] " Hans de Goede
2017-10-05 18:19 ` Andy Shevchenko
2017-10-06 16:47 ` Darren Hart
2017-10-08 18:09 ` Andy Shevchenko
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=ef9ba92b-df20-301e-e63d-6605de0246a6@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox