From: David Brownell <david-b@pacbell.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>
Subject: Re: Re: [PATCH/rfc] schedule /sys/device/.../power for removal
Date: Sun, 14 May 2006 08:51:26 -0700 [thread overview]
Message-ID: <200605140851.29221.david-b@pacbell.net> (raw)
In-Reply-To: <1147565632.21291.15.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
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.
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.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-pm@lists.osdl.org, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: [linux-pm] Re: [PATCH/rfc] schedule /sys/device/.../power for removal
Date: Sun, 14 May 2006 08:51:26 -0700 [thread overview]
Message-ID: <200605140851.29221.david-b@pacbell.net> (raw)
In-Reply-To: <1147565632.21291.15.camel@localhost.localdomain>
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.
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.
next prev parent reply other threads:[~2006-05-14 15:51 UTC|newest]
Thread overview: 25+ 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:05 ` Pavel Machek
2006-05-12 10:11 ` Andrew Morton
2006-05-12 10:11 ` Andrew Morton
2006-05-12 10:19 ` Pavel Machek
2006-05-12 10:19 ` Pavel Machek
2006-05-12 10:27 ` Andrew Morton
2006-05-12 10:27 ` Andrew Morton
2006-05-13 20:43 ` Pavel Machek
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 0:13 ` [linux-pm] " Benjamin Herrenschmidt
2006-05-14 15:51 ` David Brownell [this message]
2006-05-14 15:51 ` David Brownell
2006-05-14 16:22 ` Pavel Machek
2006-05-14 16:22 ` [linux-pm] " Pavel Machek
2006-05-14 17:45 ` David Brownell
2006-05-14 17:45 ` [linux-pm] " David Brownell
2006-05-14 0:21 ` Benjamin Herrenschmidt
2006-05-14 0:21 ` [linux-pm] " Benjamin Herrenschmidt
2006-05-14 17:48 ` David Brownell
2006-05-14 17:48 ` [linux-pm] " David Brownell
2006-05-14 23:56 ` Benjamin Herrenschmidt
2006-05-14 23:56 ` [linux-pm] " 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=200605140851.29221.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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.