From: Pavel Machek <pavel@suse.cz>
To: David Brownell <david-b@pacbell.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH/rfc] schedule /sys/device/.../power for removal
Date: Sun, 14 May 2006 18:22:37 +0200 [thread overview]
Message-ID: <20060514162236.GF2438@elf.ucw.cz> (raw)
In-Reply-To: <200605140851.29221.david-b@pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
On Ne 14-05-06 08:51:26, David Brownell wrote:
> On Saturday 13 May 2006 5:13 pm, Benjamin Herrenschmidt wrote:
> > On Fri, 2006-05-12 at 06:52 -0700, David Brownell wrote:
> > > On Friday 12 May 2006 3:11 am, Andrew Morton wrote:
> > > >
> > > > What will be impacted by this?
> > >
> > > Driver suspend/resume testing ... impact is strongly negative.
> > > ...
> > > Which IMO makes removing this a Bad Thing. It needs to have some
> > > kind of replacement in place before the "magic numbers" go away.
> >
> > And that's why Pavel is not proposing to remove it right away... but to
> > schedule it's removal so that developpers know right now that building a
> > whole new kernel<->user interface based on that is not the smartest
> > thing to do.
>
> How could we schedule the removal before we have even had a couple
> releases to fine-tune its replacement, and verify that the main issues
> with the current thing are fully resolved?
>
> ... plus, removing the whole power/* directory is clearly wrong. The
> issue that's been acknowledged is only with the contents of a single
> file, power/state, not the whole directory.
Sorry, I meant only ../state file. Fixed locally.
> There may be a bit of a gap in the process here. "July 2007" is a
> date that's not backed up by anything more than agreement that the
> current approach is a lose. Deprecation is not the same as removal.
Maybe date will need to be shifted...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-05-14 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 10:05 [PATCH/rfc] schedule /sys/device/.../power for removal Pavel Machek
2006-05-12 10:11 ` Andrew Morton
2006-05-12 10:19 ` Pavel Machek
2006-05-12 10:27 ` Andrew Morton
2006-05-13 20:43 ` Pavel Machek
2006-05-12 13:52 ` [linux-pm] " David Brownell
2006-05-14 0:13 ` Benjamin Herrenschmidt
2006-05-14 15:51 ` David Brownell
2006-05-14 16:22 ` Pavel Machek [this message]
2006-05-14 17:45 ` David Brownell
2006-05-14 0:21 ` Benjamin Herrenschmidt
2006-05-14 17:48 ` David Brownell
2006-05-14 23:56 ` Benjamin Herrenschmidt
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=20060514162236.GF2438@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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