mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mario.Limonciello@dell.com, pali.rohar@gmail.com,
	andy.shevchenko@gmail.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, 07 Feb 2018 23:50:11 +0100	[thread overview]
Message-ID: <2040799.1aJPVOsbqr@aspire.rjw.lan> (raw)
In-Reply-To: <1518009532.22495.140.camel@linux.intel.com>

On Wednesday, February 7, 2018 2:18:52 PM CET Andy Shevchenko wrote:
> On Wed, 2018-02-07 at 13:08 +0000, Mario.Limonciello@dell.com wrote:
> > > -----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.
> 
> Mario, Rafael clarifies the matter and NACKed this one (which kinda was
> expected by me, that's why RFC was in the first place).
> 
> I'm going to drop this patch from my queue.

Thanks!

  reply	other threads:[~2018-02-07 22:51 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
2018-02-07 13:18                 ` Andy Shevchenko
2018-02-07 22:50                   ` Rafael J. Wysocki [this message]
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=2040799.1aJPVOsbqr@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=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 \
    /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®