From: Mark Brown <broonie@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linaro-kernel@lists.linaro.org,
Jean Delvare <khali@linux-fr.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] ACPI: Flag use of ACPI and ACPI idioms for power supplies to regulator API
Date: Tue, 28 Jan 2014 12:21:06 +0000 [thread overview]
Message-ID: <20140128122106.GA11949@sirena.org.uk> (raw)
In-Reply-To: <15814871.c5vzFttNXX@vostro.rjw.lan>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On Tue, Jan 28, 2014 at 01:06:45AM +0100, Rafael J. Wysocki wrote:
> On Monday, January 27, 2014 01:21:06 PM Mark Brown wrote:
> > I'd like someone to take it :) . I'd expected the default thing would
> > be for it to go via the ACPI tree but I can apply it to the regulator
> > tree if you'd prefer, either way is fine by me.
> I've queued it up for my next pull request, thanks!
Excellent, thanks! Could you tag it for stable please as Jean
requested? In v3.13 it fixes regressions in lm90 on PCs if the
regulator API is enabled (which unfortunately Ubuntu did so it's
a real scenario) and it should be safe in older kernels though I'm
not aware of any actual systems that are affected.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-28 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 0:32 [PATCH] ACPI: Flag use of ACPI and ACPI idioms for power supplies to regulator API Mark Brown
2014-01-27 0:54 ` Rafael J. Wysocki
2014-01-27 0:44 ` Mark Brown
2014-01-27 12:54 ` Rafael J. Wysocki
2014-01-27 13:21 ` Mark Brown
2014-01-28 0:06 ` Rafael J. Wysocki
2014-01-28 12:21 ` Mark Brown [this message]
2014-01-28 21:55 ` Rafael J. Wysocki
2014-01-27 8:25 ` Jean Delvare
2014-01-27 10:43 ` Mark Brown
2014-01-27 14:58 ` Guenter Roeck
2014-01-27 16:25 ` Mark Brown
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=20140128122106.GA11949@sirena.org.uk \
--to=broonie@kernel.org \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux@roeck-us.net \
--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