public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: Pavel Machek <pavel@suse.cz>,
	torvalds@osdl.org, akpm@osdl.org, linux-pm@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] [PATCH 3/5] [pm] Respect the actual device power states in sysfs interface
Date: Mon, 20 Feb 2006 14:04:04 -0800	[thread overview]
Message-ID: <20060220220404.GA25746@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0602200955030.12708-100000@monsoon.he.net>

On Mon, Feb 20, 2006 at 09:58:27AM -0800, Patrick Mochel wrote:
> 
> On Sun, 19 Feb 2006, Greg KH wrote:
> 
> > On Sun, Feb 19, 2006 at 03:59:25PM -0800, Patrick Mochel wrote:
> > >
> > > On Sat, 18 Feb 2006, Pavel Machek wrote:
> > >
> > > > Hi!
> > > >
> > > > > Fix the per-device state file to respect the actual state that
> > > > > is reported by the device, or written to the file.
> > > >
> > > > Can we let "state" file die? You actually suggested that at one point.
> > > >
> > > > I do not think passing states in u32 is good idea. New interface that passes
> > > > state as string would probably be better.
> > >
> > > Yup, in the future that will be better. For now, let's work with what we
> > > got and fix 2.6.16 to be compatible with previous versions..
> >
> > It's _way_ too late in the 2.6.16 cycle for this series of patches, if
> > that is what you are proposing.
> 
> Would you mind commmenting on why, as well as your opinion on the validity
> of the patches themselves?
> 
> This static, hardcoded policy was introduced into the core ~2 weeks ago,
> and it doesn't seem like it belongs there at all.

That patch was accepted as it fixed a oops.  It also went in for
2.6.16-rc2, which is much earlier than 2.6.16-rc4, and it had been in
the -mm tree for quite a while for people to test it out and verify that
it didn't break anything.  I didn't hear any complaints about it, so
that is why it went in.

In contrast, this patch series creates a new api and doesn't necessarily
fix any reported bugs.  It also has not had the time to be tested in the
-mm tree, and there is quite a lot of disagreement about the patches on
the lists.  All of that combinded makes it not acceptable for so late in
the -rc cycle (remember, -rc4 means only serious bug fixes.)

> This seems like the easiest way to fixing it, but I'm open to
> alternative suggestions..

Care to resend the series based on all of the comments you have
addressed so far?  I'll be glad to review it then.

thanks,

greg k-h

  reply	other threads:[~2006-02-20 22:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18  2:03 [PATCH 3/5] [pm] Respect the actual device power states in sysfs interface Patrick Mochel
2006-02-18 15:55 ` [linux-pm] " Pavel Machek
2006-02-19 23:59   ` Patrick Mochel
2006-02-20  0:09     ` Pavel Machek
2006-02-20  0:17       ` Patrick Mochel
2006-02-20  0:20         ` Pavel Machek
2006-02-20  0:36           ` Patrick Mochel
2006-02-20  0:41             ` Pavel Machek
2006-02-20 17:55               ` Patrick Mochel
2006-02-20 17:58                 ` Pavel Machek
2006-02-20 18:08                   ` Patrick Mochel
2006-02-20 18:10                     ` Pavel Machek
2006-02-20  0:46     ` Greg KH
2006-02-20 17:58       ` Patrick Mochel
2006-02-20 22:04         ` Greg KH [this message]
2006-02-21  1:09           ` Patrick Mochel
2006-02-21 10:57             ` Pavel Machek
2006-02-21 11:12               ` Patrick Mochel
2006-02-21 11:25                 ` Pavel Machek
2006-02-27 19:06                   ` Patrick Mochel

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=20060220220404.GA25746@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=mochel@digitalimplant.org \
    --cc=pavel@suse.cz \
    --cc=torvalds@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