From: Pavel Machek <pavel@ucw.cz>
To: rae l <crquan@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Christoph Hellwig <hch@lst.de>,
Dominik Brodowski <linux@brodo.de>, Adrian Bunk <bunk@stusta.de>,
Arjan van de Ven <arjan@linux.intel.com>,
Nick Piggin <npiggin@suse.de>, Len Brown <len.brown@intel.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: many items in Documentation/feature-removal-schedule.txt have expired, please update
Date: Thu, 20 Mar 2008 21:22:16 +0100 [thread overview]
Message-ID: <20080320202215.GD4397@ucw.cz> (raw)
In-Reply-To: <91b13c310803200622k6a302851nc97774615f2ef3ee@mail.gmail.com>
On Thu 2008-03-20 21:22:29, rae l wrote:
> I noticed that many feature removal schedule marked in this file have
> expired, so please update information:
> 1. if the feature has been removed, please remove it from this file;
> 2. if it does not, please update the schedule date;
> What: dev->power.power_state
> When: July 2007
> Why: Broken design for runtime control over driver power states, confusing
> driver-internal runtime power management with: mechanisms to support
> system-wide sleep state transitions; event codes that distinguish
> different phases of swsusp "sleep" transitions; and userspace policy
> inputs. This framework was never widely used, and most attempts to
> use it were broken. Drivers should instead be exposing domain-specific
> interfaces either to kernel or to userspace.
> Who: Pavel Machek <pavel@suse.cz>
Feel free to help killing remaining power_state users, then it can
disappear.
I won't update the date: it is in past to remind people that it should
have been killed already.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-03-20 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 13:22 many items in Documentation/feature-removal-schedule.txt have expired, please update rae l
2008-03-20 13:25 ` Christoph Hellwig
2008-03-20 16:15 ` Harvey Harrison
2008-03-20 20:22 ` Pavel Machek [this message]
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=20080320202215.GD4397@ucw.cz \
--to=pavel@ucw.cz \
--cc=arjan@linux.intel.com \
--cc=bunk@stusta.de \
--cc=crquan@gmail.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=npiggin@suse.de \
--cc=shemminger@linux-foundation.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