public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org,
	linux-pm@osdl.org
Subject: Re: [PATCH 3/5] [pm] Respect the actual device power states in sysfs interface
Date: Tue, 21 Feb 2006 11:57:11 +0100	[thread overview]
Message-ID: <20060221105711.GK21557@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.50.0602201655580.21145-100000@monsoon.he.net>

[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]

On Po 20-02-06 17:09:26, Patrick Mochel wrote:
> 
> On Mon, 20 Feb 2006, Greg KH wrote:
> 
> > On Mon, Feb 20, 2006 at 09:58:27AM -0800, Patrick Mochel wrote:
> 
> > > 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.)
> 
> Thanks.
> 
> However, there are a couple of things to note:
> 
> - These patches don't create a new API; they fix the semantics of an
>   existing API by restoring them to its originally designed semantics.

They may reintroduce "original" semantics, but they'll break
applications needing 2.6.15 semantic (where 2 meant D3hot).

> - The BUG() still exists and is relatively easily triggerable (by calling
>   pci_choose_state() with the wrong value). The fact that the BUG() was
>   allowed into the kernel is surprising - the mantra for a long time has
>   been that no new BUG()s should be added. This one is easily made nicer
>   (see patch 4/4 in the next series), so I don't see why it wasn't
>   targeted before..

I don't know what you are talking about here. "No new BUGs"?! It is
bad to have bug triggerable from userspace, but that was fixed.

								Pavel
-- 
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-02-21 10:57 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 ` 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                     ` [linux-pm] " Pavel Machek
2006-02-20  0:46     ` Greg KH
2006-02-20 17:58       ` [linux-pm] " Patrick Mochel
2006-02-20 22:04         ` Greg KH
2006-02-21  1:09           ` Patrick Mochel
2006-02-21 10:57             ` Pavel Machek [this message]
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=20060221105711.GK21557@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=mochel@digitalimplant.org \
    --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