[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150117012625.GU3843@piout.net>
Date: Sat, 17 Jan 2015 02:26:25 +0100
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: John Stultz <john.stultz@...aro.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Nicolas Ferre <nicolas.ferre@...el.com>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
Russell King - ARM Linux <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] clocksource: track usage
Hi,
On 16/01/2015 at 11:05:46 -0800, John Stultz wrote :
> On Fri, Jan 16, 2015 at 8:57 AM, Alexandre Belloni
> <alexandre.belloni@...e-electrons.com> wrote:
> > Track whether the clocksource is enabled or disabled.
>
>
> So.. this commit message needs work. Why do we care to track the
> clocksource enabled/disabled state?
>
What about:
Track whether the clocksource is enabled or disabled. This will allow to
select whether an action is necessary, for example suspend or resume.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists