From: Greg KH <greg@kroah.com>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: akpm@osdl.org, linux-pm@osdl.org, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Fix runtime device suspend/resumre interface
Date: Tue, 21 Feb 2006 09:49:50 -0800 [thread overview]
Message-ID: <20060221174950.GA23054@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0602201641380.21145-100000@monsoon.he.net>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Mon, Feb 20, 2006 at 04:55:34PM -0800, Patrick Mochel wrote:
>
> Hi there,
>
> Here is an updated version of the patches to fix the sysfs interface for
> runtime device power management by restoring the file to its originally
> designed behavior - to place devices in the power state specified by the
> user process writing to the file.
>
> Recently, the interface was changed to filter out values to prevent a
> BUG() that was introduced in the PCI power management code. While a valid
> fix, it makes the driver core filter values that might otherwise be used
> by the bus/device drivers.
Are there any existing bus/device drivers that are currently broken
because of this change?
thanks,
greg k-h
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
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 0/4] Fix runtime device suspend/resumre interface
Date: Tue, 21 Feb 2006 09:49:50 -0800 [thread overview]
Message-ID: <20060221174950.GA23054@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0602201641380.21145-100000@monsoon.he.net>
On Mon, Feb 20, 2006 at 04:55:34PM -0800, Patrick Mochel wrote:
>
> Hi there,
>
> Here is an updated version of the patches to fix the sysfs interface for
> runtime device power management by restoring the file to its originally
> designed behavior - to place devices in the power state specified by the
> user process writing to the file.
>
> Recently, the interface was changed to filter out values to prevent a
> BUG() that was introduced in the PCI power management code. While a valid
> fix, it makes the driver core filter values that might otherwise be used
> by the bus/device drivers.
Are there any existing bus/device drivers that are currently broken
because of this change?
thanks,
greg k-h
next prev parent reply other threads:[~2006-02-21 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 0:55 [PATCH 0/4] Fix runtime device suspend/resumre interface Patrick Mochel
2006-02-21 0:55 ` Patrick Mochel
2006-02-21 17:49 ` Greg KH [this message]
2006-02-21 17:49 ` Greg KH
2006-02-27 19:18 ` Patrick Mochel
2006-02-27 19:18 ` Patrick Mochel
2006-03-01 0:38 ` Greg KH
2006-03-01 11:31 ` Rafael J. Wysocki
2006-03-01 11:31 ` Rafael J. Wysocki
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=20060221174950.GA23054@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=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 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.