From: <Mario.Limonciello@dell.com>
To: <andriy.shevchenko@linux.intel.com>, <dvhart@infradead.org>
Cc: <platform-driver-x86@vger.kernel.org>, <acelan.kao@canonical.com>,
<linux-kernel@vger.kernel.org>, <pali.rohar@gmail.com>,
<rjw@rjwysocki.net>
Subject: RE: [RFC, PATCH v1] platform/x86: intel-vbtn: Convert to pure ACPI driver
Date: Tue, 6 Feb 2018 20:33:54 +0000 [thread overview]
Message-ID: <c51e36664a6e4df6b641f3c684b0d189@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <1517847491.22495.36.camel@linux.intel.com>
> -----Original Message-----
> From: platform-driver-x86-owner@vger.kernel.org [mailto:platform-driver-x86-
> owner@vger.kernel.org] On Behalf Of Andy Shevchenko
> Sent: Monday, February 5, 2018 10:18 AM
> To: Darren Hart <dvhart@infradead.org>
> Cc: platform-driver-x86@vger.kernel.org; AceLan Kao
> <acelan.kao@canonical.com>; linux-kernel@vger.kernel.org;
> pali.rohar@gmail.com; Limonciello, Mario <Mario_Limonciello@Dell.com>; Rafael
> Wysocki <rjw@rjwysocki.net>
> Subject: Re: [RFC, PATCH v1] platform/x86: intel-vbtn: Convert to pure ACPI driver
>
> On Wed, 2018-01-31 at 13:37 -0800, Darren Hart wrote:
> > On Wed, Jan 31, 2018 at 08:26:14PM +0200, Andy Shevchenko wrote:
> > > Remove code duplication by converting driver to pure ACPI one.
> >
>
> I have fixed couple issues, but...
>
> > +Rafael
> >
> > I don't see any reason *not* to do this, it seems the acpi driver
> > model provides
> > some of the boilerplate stuff we were doing manually before as a
> > platform
> > device. I'm scratching my head wondering why we did this as a
> > platform-driver in
> > the first place now...
>
> ...I still keep in my review queue in a hope that someone can actually
> test this on real hardware.
>
> --
> Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Intel Finland Oy
Andy,
I'm pretty sure XPS 9365 can test this. I was going to try but
https://patchwork.kernel.org/patch/10194503/ was not
able to compile on top of platform-x86/for-next.
That was the only one I saw at patchwork.
drivers/platform/x86/intel-vbtn.c:172:11: error: ‘ACPI_BUTTON_CLASS’ undeclared here (not in a function)
.class = ACPI_BUTTON_CLASS,
^
drivers/platform/x86/intel-vbtn.c:178:2: error: unknown field ‘driver’ specified in initializer
.driver = {
^
scripts/Makefile.build:316: recipe for target 'drivers/platform/x86/intel-vbtn.o' failed
make[5]: *** [drivers/platform/x86/intel-vbtn.o] Error 1
is that different than the one in your review queue?
Thanks,
next prev parent reply other threads:[~2018-02-06 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 18:26 Andy Shevchenko
2018-01-31 21:37 ` Darren Hart
2018-02-05 16:18 ` Andy Shevchenko
2018-02-06 20:33 ` Mario.Limonciello [this message]
[not found] ` <CAHp75VeFSuQYu67DdnJDjZDoaLZiPuo7ag7Lz0q6eSCDjayobw@mail.gmail.com>
2018-02-07 1:57 ` Mario.Limonciello
2018-02-07 9:31 ` Rafael J. Wysocki
2018-02-07 9:47 ` Rafael J. Wysocki
2018-02-07 9:55 ` Pali Rohár
2018-02-07 13:08 ` Mario.Limonciello
2018-02-07 13:18 ` Andy Shevchenko
2018-02-07 22:50 ` Rafael J. Wysocki
2018-02-07 22:33 ` Rafael J. Wysocki
2018-02-07 9:44 ` Rafael J. Wysocki
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=c51e36664a6e4df6b641f3c684b0d189@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=acelan.kao@canonical.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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
all inboxes | Powered by JetHome®