From: Darren Hart <dvhart@infradead.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Andy Shevchenko <andy@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RFC: platform/x86: wmi: Fix check for method instance number
Date: Wed, 14 Jun 2017 13:39:06 -0700 [thread overview]
Message-ID: <20170614203906.GE22450@fury> (raw)
In-Reply-To: <20170614154654.GA22981@pali>
On Wed, Jun 14, 2017 at 05:46:54PM +0200, Pali Rohár wrote:
> On Tuesday 13 June 2017 11:42:28 Darren Hart wrote:
> > On Tue, Jun 13, 2017 at 08:04:57PM +0200, Pali Rohár wrote:
> > > On Tuesday 13 June 2017 18:49:51 Darren Hart wrote:
> > > > I'd suggest reaching out to the maintainers and contributors to the
> > > > drivers you mention to request some help in testing.
> > >
> > > Seems sane. Grep for all methods with instance number different as zero
> > > (or just number one -- which can be suspicious as somebody could thought
> > > that indexing is from one, not zer) and try to receive ACPI/BMOF data
> > > and verify it.
> >
> > This would still be the ideal solution, verify we can do the right thing
> > without breaking existing drivers. Agreed.
>
> Here is all usage:
>
Thanks for pulling this together Pali.
...
> So problematic drivers which use instance=1 without any comments are:
>
> acer-wmi
> alienware-wmi
> asus-wmi
> dell-wmi-led
> mxm-wmi
>
I'd suggest adding a WARN_ONCE() when instance >= instance_count (I guess only
== concerns us) as a way to draw out any problematic usage. We can let that go
while we try to collect data from the other driver maintainers and see if it
generates any more hits.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2017-06-14 20:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 11:55 [PATCH] RFC: platform/x86: wmi: Fix check for method instance number Pali Rohár
2017-06-10 19:15 ` Pali Rohár
2017-06-13 16:49 ` Darren Hart
2017-06-13 18:04 ` Pali Rohár
2017-06-13 18:42 ` Darren Hart
2017-06-14 15:46 ` Pali Rohár
2017-06-14 20:39 ` Darren Hart [this message]
2017-06-15 13:59 ` Pali Rohár
2017-06-15 15:16 ` Mario.Limonciello
2017-06-16 16:33 ` Mario.Limonciello
2017-06-17 16:34 ` Pali Rohár
2017-06-21 21:52 ` Mario.Limonciello
2017-06-22 7:33 ` Pali Rohár
2017-06-17 16:47 ` Pali Rohár
2017-06-19 15:02 ` joeyli
2017-07-05 9:51 ` Pali Rohár
2017-07-05 19:30 ` David Airlie
2017-07-05 20:24 ` Pali Rohár
2017-08-06 15:35 ` Pali Rohár
2017-08-06 16:10 ` Andy Shevchenko
2017-08-06 20:21 ` Pali Rohár
2017-08-06 15:42 ` Pali Rohár
2017-08-06 16:18 ` Hans de Goede
2017-08-06 20:16 ` Pali Rohár
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=20170614203906.GE22450@fury \
--to=dvhart@infradead.org \
--cc=andy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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