From: Darren Hart <dvhart@infradead.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Corentin Chary" <corentin.chary@gmail.com>,
"Andy Shevchenko" <andy@infradead.org>,
acpi4asus-user <acpi4asus-user@lists.sourceforge.net>,
"Platform Driver" <platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] platform/x86: Fix check for method instance number
Date: Thu, 17 Aug 2017 08:25:25 -0700 [thread overview]
Message-ID: <20170817152525.GB19276@fury> (raw)
In-Reply-To: <CAHp75Ve-umOB8U2HZ7iVf-0HfQX=A3-7KanEa0AY=iEhWpFuaA@mail.gmail.com>
On Sun, Aug 13, 2017 at 03:54:26PM +0300, Andy Shevchenko wrote:
> On Sat, Aug 12, 2017 at 10:44 AM, Pali Rohár <pali.rohar@gmail.com> wrote:
> > This patch series fixes remaining mxm-wmi and asus-wmi drivers to evaluate
> > WMI methods with correct and available instance number. Now all WMI drivers
> > should call WMI functions with correct instance number and last patch fixes
> > WMI check for invalid instances. Patch for paeq-wmi is optional as machine
> > has 10 instances but instance number is ignored at all. But for consistency
> > with other drivers first instance would be used (instead of second).
> >
>
> I pushed first 3 to testing, which seems to me right thing to do, and
> left the last one to be ACK by Darren and/or others (I'm not familiar
> so far with that code).
Reviewed with one question to Pali. Since you merged 1-3, I'll leave 4 to you
unless you prefer I merge it.
> Thanks!
>
> > Pali Rohár (4):
> > platform/x86: mxm-wmi: Evaluate wmi method with instance number 0x0
> > platform/x86: asus-wmi: Evaluate wmi method with instance number 0x0
> > platform/x86: peaq-wmi: Evaluate wmi method with instance number 0x0
> > platform/x86: wmi: Fix check for method instance number
> >
> > drivers/platform/x86/asus-wmi.c | 4 ++--
> > drivers/platform/x86/mxm-wmi.c | 4 ++--
> > drivers/platform/x86/peaq-wmi.c | 2 +-
> > drivers/platform/x86/wmi.c | 6 +++---
> > 4 files changed, 8 insertions(+), 8 deletions(-)
> >
> > --
> > 1.7.9.5
> >
>
>
>
> --
> With Best Regards,
> Andy Shevchenko
>
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2017-08-17 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 7:44 [PATCH 0/4] platform/x86: Fix check for method instance number Pali Rohár
2017-08-12 7:44 ` [PATCH 1/4] platform/x86: mxm-wmi: Evaluate wmi method with instance number 0x0 Pali Rohár
2017-08-12 7:44 ` [PATCH 2/4] platform/x86: asus-wmi: " Pali Rohár
2017-08-12 7:44 ` [PATCH 3/4] platform/x86: peaq-wmi: " Pali Rohár
2017-08-12 20:12 ` Hans de Goede
2017-08-12 7:44 ` [PATCH 4/4] platform/x86: wmi: Fix check for method instance number Pali Rohár
2017-08-17 15:24 ` Darren Hart
2017-08-17 21:13 ` Pali Rohár
2017-08-17 21:36 ` Darren Hart
2017-08-18 12:20 ` Andy Shevchenko
2017-08-13 12:54 ` [PATCH 0/4] platform/x86: " Andy Shevchenko
2017-08-17 15:25 ` Darren Hart [this message]
2017-08-17 17:31 ` 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=20170817152525.GB19276@fury \
--to=dvhart@infradead.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=corentin.chary@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--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