From: "Pali Rohár" <pali.rohar@gmail.com>
To: "Michał Kępień" <kernel@kempniu.pl>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Darren Hart <dvhart@infradead.org>,
Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Andy Lutomirski <luto@kernel.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fixes for dell-wmi
Date: Mon, 28 Dec 2015 14:46:36 +0100 [thread overview]
Message-ID: <201512281446.36868@pali> (raw)
In-Reply-To: <20151228133317.GA7540@eudyptula.hq.kempniu.pl>
[-- Attachment #1: Type: Text/Plain, Size: 966 bytes --]
On Monday 28 December 2015 14:33:17 Michał Kępień wrote:
> > This patch series adds check if Dell WMI descriptor structure is
> > valid and fixes processing WMI events on devices with WMI
> > interface version 0.
> >
> > After testing, second patch is good candidate for backporting into
> > stable kernels, but problem is that it cannot be used without
> > first patch. So I let decision to other people.
> >
> > Gabriele and Michał, this patch series should fix processing events
> > on yours Dell laptops (you have in DSDT defined version 0). Can
> > you test it?
>
> My Vostro V131 (and any other as well, judging from the DSDT dumps I
> found scattered around the web) has the WMI Interface Version field
> set to 1, as the first one of your patches correctly asserts.
Ok, great. Can you post DEBUG output when receiving events before and
after patch (to check that processing is correct)?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-12-28 13:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 21:18 [PATCH 0/2] Fixes for dell-wmi Pali Rohár
2015-12-24 21:18 ` [PATCH 1/2] dell-wmi: Check if Dell WMI descriptor structure is valid Pali Rohár
2015-12-25 1:23 ` Andy Lutomirski
2015-12-25 13:02 ` Pali Rohár
2015-12-28 13:37 ` Michał Kępień
2015-12-28 14:08 ` Pali Rohár
2015-12-29 12:44 ` Michał Kępień
2015-12-29 16:05 ` Pali Rohár
2015-12-30 11:27 ` Michał Kępień
2016-01-04 18:23 ` Andy Lutomirski
2015-12-24 21:18 ` [PATCH 2/2] dell-wmi: Process only one event on devices with interface version 0 Pali Rohár
2015-12-28 13:40 ` Michał Kępień
2015-12-28 13:49 ` Pali Rohár
2015-12-27 12:59 ` [PATCH 0/2] Fixes for dell-wmi Gabriele Mazzotta
2015-12-27 13:07 ` Pali Rohár
2015-12-27 13:10 ` Gabriele Mazzotta
2015-12-27 13:17 ` Pali Rohár
2015-12-28 13:33 ` Michał Kępień
2015-12-28 13:46 ` Pali Rohár [this message]
2015-12-29 12:18 ` Michał Kępień
2016-01-04 20:48 ` Darren Hart
2016-01-07 22:31 ` Pali Rohár
2016-01-04 21:26 ` [PATCH v2 " Pali Rohár
2016-01-04 21:26 ` [PATCH v2 1/2] dell-wmi: Check if Dell WMI descriptor structure is valid Pali Rohár
2016-01-04 21:26 ` [PATCH v2 2/2] dell-wmi: Process only one event on devices with interface version 0 Pali Rohár
2016-01-12 11:14 ` Michał Kępień
2016-01-12 17:49 ` Pali Rohár
2016-01-12 20:12 ` Michał Kępień
2016-01-14 23:06 ` Darren Hart
2016-01-11 19:22 ` [PATCH v2 0/2] Fixes for dell-wmi Darren Hart
2016-01-12 0:30 ` Gabriele Mazzotta
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=201512281446.36868@pali \
--to=pali.rohar@gmail.com \
--cc=dvhart@infradead.org \
--cc=gabriele.mzt@gmail.com \
--cc=kernel@kempniu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mjg59@srcf.ucam.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox