From: "Pali Rohár" <pali.rohar@gmail.com>
To: Darren Hart <dvhart@infradead.org>,
Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Andy Lutomirski <luto@kernel.org>,
Alex Hung <alex.hung@canonical.com>
Cc: "Matthew Garrett" <mjg59@srcf.ucam.org>,
"Michał Kępień" <kernel@kempniu.pl>,
"Mario Limonciello" <mario_limonciello@dell.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] dell-wmi: Changes in WMI event code handling
Date: Thu, 16 Jun 2016 09:33:02 +0200 [thread overview]
Message-ID: <20160616073302.GT29844@pali> (raw)
In-Reply-To: <20160616031958.GA54214@f23x64.localdomain>
On Wednesday 15 June 2016 20:19:58 Darren Hart wrote:
> On Wed, Jun 15, 2016 at 09:49:09PM +0200, Pali Rohár wrote:
> > First patch describe problem about 0xe045 code. Second and third are just
> > cosmetic and last rework code which processing WMI events. It should be
> > properly tested on more Dell machines, to check that everything is still
> > working correctly.
>
> Is this "should be properly tested on more Dell machines" still the case? Are
> you ready for this to go into linux-next?
Series should be OK, but I would like to see if someone else test this
series... Gabriele, Alex or Andy? Do you have time?
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2016-06-16 7:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 19:49 [PATCH v3 0/4] dell-wmi: Changes in WMI event code handling Pali Rohár
2016-06-15 19:49 ` [PATCH v3 1/4] dell-wmi: Ignore WMI event code 0xe045 Pali Rohár
2016-06-15 19:49 ` [PATCH v3 2/4] dell-wmi: Sort WMI event codes and update comments Pali Rohár
2016-06-15 19:49 ` [PATCH v3 3/4] dell-wmi: Add information about other WMI event codes Pali Rohár
2016-06-15 19:49 ` [PATCH v3 4/4] dell-wmi: Generate one sparse keymap for all machines Pali Rohár
2016-06-16 3:19 ` [PATCH v3 0/4] dell-wmi: Changes in WMI event code handling Darren Hart
2016-06-16 7:33 ` Pali Rohár [this message]
2016-06-16 23:01 ` Gabriele Mazzotta
2016-06-21 16:27 ` Darren Hart
2016-06-21 18:06 ` Darren Hart
2016-06-21 18:16 ` Mario_Limonciello
2016-06-21 18:29 ` Pali Rohár
2016-06-21 18:37 ` Mario_Limonciello
2016-06-22 10:30 ` Pali Rohár
2016-06-22 13:20 ` Mario_Limonciello
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=20160616073302.GT29844@pali \
--to=pali.rohar@gmail.com \
--cc=alex.hung@canonical.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=mario_limonciello@dell.com \
--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;
as well as URLs for NNTP newsgroup(s).