[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100527223418.281a687f@lxorguk.ukuu.org.uk>
Date: Thu, 27 May 2010 22:34:18 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Peter Zijlstra <peterz@...radead.org>,
Felipe Balbi <felipe.balbi@...ia.com>,
Thomas Gleixner <tglx@...utronix.de>,
Arve Hjønnevåg <arve@...roid.com>,
LKML <linux-kernel@...r.kernel.org>,
Florian Mickler <florian@...kler.org>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
Linux PM <linux-pm@...ts.linux-foundation.org>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8)
On Thu, 27 May 2010 13:29:18 -0400 (EDT)
Alan Stern <stern@...land.harvard.edu> wrote:
> On Thu, 27 May 2010, Peter Zijlstra wrote:
>
> > On Thu, 2010-05-27 at 13:04 -0400, Alan Stern wrote:
> > >
> > > Does this mean you believe "echo mem >/sys/power/state" is bad and
> > > should be removed? Or "echo disk >/sys/power/state"? They pay no
> > > attention to latencies or other requirements.
> >
> > Those are a whole different beast, those are basically a quick-off
> > button like thing. Forced suspend is conceptually a very different beast
> > from power-saving a running system.
>
> They may be different conceptually. Nevertheless, Android uses forced
> suspend as a form of power saving. Until better mechanisms are in
> place, it makes sense.
For them, not for Linux.
Several vendors have exciting kernel drivers that do things like binary
patch other modules. Until better mechanisms are in place it does *NOT*
make sense to merge such stuff.
I don't care what they do in their own tree (consenting adults in their
own home and all that) but what they do in the public tree is another
matter.
Alan
--
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