From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Fulvio <fbf@libero.it>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
linux-pm@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>,
Nadav Haklai <nadavh@marvell.com>
Subject: Re: [PATCH] cpuidle: mvebu: Fix the CPU PM notifier usage
Date: Wed, 04 Mar 2015 15:34:06 +0100 [thread overview]
Message-ID: <54F717DE.80106@linaro.org> (raw)
In-Reply-To: <3654949.JbH3Ca4PON@vostro.rjw.lan>
On 03/04/2015 03:53 PM, Rafael J. Wysocki wrote:
> On Tuesday, March 03, 2015 04:20:26 PM Daniel Lezcano wrote:
>> On 03/03/2015 03:58 PM, Fulvio wrote:
[ ... ]
>> The fix is correct. The cpu_pm_enter/exit symmetry must be kept because
>> we don't know what the notifier clients are doing.
>>
>> The point is : can we send it to stable@ as a bug fix or not ?
>
> Yes, we can, unless there's a risk of breaking things that cannot be
> ignored.
Ok, I added the stable@ tag.
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpuidle: mvebu: Fix the CPU PM notifier usage
Date: Wed, 04 Mar 2015 15:34:06 +0100 [thread overview]
Message-ID: <54F717DE.80106@linaro.org> (raw)
In-Reply-To: <3654949.JbH3Ca4PON@vostro.rjw.lan>
On 03/04/2015 03:53 PM, Rafael J. Wysocki wrote:
> On Tuesday, March 03, 2015 04:20:26 PM Daniel Lezcano wrote:
>> On 03/03/2015 03:58 PM, Fulvio wrote:
[ ... ]
>> The fix is correct. The cpu_pm_enter/exit symmetry must be kept because
>> we don't know what the notifier clients are doing.
>>
>> The point is : can we send it to stable@ as a bug fix or not ?
>
> Yes, we can, unless there's a risk of breaking things that cannot be
> ignored.
Ok, I added the stable@ tag.
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-03-04 14:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 17:20 [PATCH] cpuidle: mvebu: Fix the CPU PM notifier usage Gregory CLEMENT
2015-02-26 17:20 ` Gregory CLEMENT
2015-02-26 21:55 ` Rafael J. Wysocki
2015-02-26 21:55 ` Rafael J. Wysocki
2015-02-27 9:39 ` Gregory CLEMENT
2015-02-27 9:39 ` Gregory CLEMENT
2015-03-03 10:30 ` Daniel Lezcano
2015-03-03 10:30 ` Daniel Lezcano
2015-03-03 10:34 ` Gregory CLEMENT
2015-03-03 10:34 ` Gregory CLEMENT
2015-03-03 10:52 ` Fulvio
2015-03-03 10:52 ` Fulvio
2015-03-03 11:12 ` Daniel Lezcano
2015-03-03 11:12 ` Daniel Lezcano
2015-03-03 12:51 ` Gregory CLEMENT
2015-03-03 12:51 ` Gregory CLEMENT
2015-03-03 13:00 ` Daniel Lezcano
2015-03-03 13:00 ` Daniel Lezcano
2015-03-03 14:58 ` Fulvio
2015-03-03 14:58 ` Fulvio
2015-03-03 15:20 ` Daniel Lezcano
2015-03-03 15:20 ` Daniel Lezcano
2015-03-04 14:53 ` Rafael J. Wysocki
2015-03-04 14:53 ` Rafael J. Wysocki
2015-03-04 14:34 ` Daniel Lezcano [this message]
2015-03-04 14:34 ` Daniel Lezcano
2015-02-27 16:50 ` Daniel Lezcano
2015-02-27 16:50 ` Daniel Lezcano
2015-02-27 22:18 ` Rafael J. Wysocki
2015-02-27 22:18 ` 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=54F717DE.80106@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=boris.brezillon@free-electrons.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=fbf@libero.it \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=nadavh@marvell.com \
--cc=rjw@rjwysocki.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.