From: <Mario.Limonciello@dell.com>
To: <pali.rohar@gmail.com>, <rjw@rjwysocki.net>
Cc: <andy.shevchenko@gmail.com>, <andriy.shevchenko@linux.intel.com>,
<dvhart@infradead.org>, <platform-driver-x86@vger.kernel.org>,
<acelan.kao@canonical.com>, <linux-kernel@vger.kernel.org>
Subject: RE: [RFC, PATCH v1] platform/x86: intel-vbtn: Convert to pure ACPI driver
Date: Wed, 7 Feb 2018 13:08:08 +0000 [thread overview]
Message-ID: <8d143fabe24f43de933dc60ce6480d00@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <20180207095522.qhs2wns4goif76u3@pali>
> -----Original Message-----
> From: Pali Rohár [mailto:pali.rohar@gmail.com]
> Sent: Wednesday, February 7, 2018 3:55 AM
> To: Rafael J. Wysocki <rjw@rjwysocki.net>
> Cc: Andy Shevchenko <andy.shevchenko@gmail.com>; Limonciello, Mario
> <Mario_Limonciello@Dell.com>; andriy.shevchenko@linux.intel.com;
> dvhart@infradead.org; platform-driver-x86@vger.kernel.org;
> acelan.kao@canonical.com; linux-kernel@vger.kernel.org
> Subject: Re: [RFC, PATCH v1] platform/x86: intel-vbtn: Convert to pure ACPI driver
>
> On Wednesday 07 February 2018 10:47:57 Rafael J. Wysocki wrote:
> > BTW, please CC patches with ACPI material to linux-acpi. They are less likely
> > to be overlooked by me then and the others on that list may have opinions on
> > them too.
>
> Maybe we can update MAINTAINERS file for acpi based platform-x86 drivers
> to include linux-acpi list? Darren, Andy, any idea?
>
I would also wonder if the intel-vbtn driver should still live in platform-x86 as it's
now pure ACPI driver with this change Andy proposed.
Btw Andy for your v2 with your fixups that were in your review branch feel free
to add:
Tested-by: Mario Limonciello <mario.limonciello@dell.com>
When you resubmit it.
next prev parent reply other threads:[~2018-02-07 13:08 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
[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 [this message]
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=8d143fabe24f43de933dc60ce6480d00@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=acelan.kao@canonical.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.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®