From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Sebastian Reichel <sre@kernel.org>,
Lukas Wunner <lukas@wunner.de>,
Robert Moore <robert.moore@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v7 0/5] ACPI: new acpi_dev_present helper + ac and battery blacklist patches
Date: Thu, 20 Apr 2017 11:20:09 +0300 [thread overview]
Message-ID: <1492676409.24567.92.camel@linux.intel.com> (raw)
In-Reply-To: <20170419203340.GI2619@lahna.fi.intel.com>
On Wed, 2017-04-19 at 23:33 +0300, Mika Westerberg wrote:
> On Wed, Apr 19, 2017 at 09:37:50PM +0200, Rafael J. Wysocki wrote:
> > On Wed, Apr 19, 2017 at 2:02 PM, Hans de Goede <hdegoede@redhat.com>
> > wrote:
> > > Hi Rafael,
> > >
> > > This is a new version of my acpi_dev_present helper + ac and
> > > battery
> > > blacklist patches, new compared to the v5 resend of the latest
> > > version of all these patches are some changes to the first,
> > > third and fourth patch as requested by Andy Shevchenko.
> > >
> > > This set also includes a power-supply patch, which depends on the
> > > new acpi_dev_present helper and has an Ack from Sebastian Reichel
> > > (the power-supply maintainer) for being merged through the ACPI
> > > tree because of that dependency.
> > >
> > > These patches obsolete:
> > > -earlier versions of patches with the same title
> > > -"ACPI: battery: Add acpi_battery_unregister() function"
> > > -"ACPI: ac: Add acpi_ac_unregister() function"
> > > -"power: supply: axp288_fuel_gauge: Unregister duplicate ACPI
> > > battery supply"
> > > -"power: supply: axp288_charger: Unregister duplicate ACPI ac
> > > supply"
> >
> > Andy, Mika, any concerns about anything this series?
>
> No concerns from my side.
Neither from mine.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-04-20 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 12:02 [PATCH v7 0/5] ACPI: new acpi_dev_present helper + ac and battery blacklist patches Hans de Goede
2017-04-19 12:02 ` [PATCH v7 1/5] ACPI: utils: Add new acpi_dev_present helper Hans de Goede
2017-04-19 12:02 ` [PATCH v7 2/5] ACPI: battery: Fix acpi_battery_exit on acpi_battery_init_async errors Hans de Goede
2017-04-19 12:02 ` [PATCH v7 3/5] ACPI: battery: Add a blacklist with PMIC ACPI HIDs with a native battery driver Hans de Goede
2017-04-19 12:02 ` [PATCH v7 4/5] ACPI: ac: Add a blacklist with PMIC ACPI HIDs with a native charger driver Hans de Goede
2017-04-19 12:02 ` [PATCH v7 5/5] power: supply: axp288_charger: Only wait for INT3496 device if present Hans de Goede
2017-04-19 19:37 ` [PATCH v7 0/5] ACPI: new acpi_dev_present helper + ac and battery blacklist patches Rafael J. Wysocki
2017-04-19 20:33 ` Mika Westerberg
2017-04-20 8:20 ` Andy Shevchenko [this message]
2017-04-20 10:38 ` 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=1492676409.24567.92.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).