From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-kernel@vger.kernel.org, linux-pm@lists.osdl.org
Subject: Userspace interface breakage in power/state
Date: Mon, 16 Jan 2006 00:27:03 +0000 [thread overview]
Message-ID: <20060116002703.GA4769@srcf.ucam.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
(Resent, without the wrong address for lkml)
In older kernels, power/state for PCI devices took a PCI power state as
an argument and so "3" was an entirely sensible thing to echo into it.
In current kernels, it hits a BUG() in pci_choose_state and things blow
up.
While I realise that the former interface was broken and wrong, would it
be possible to move to a new one without breaking existing code?
--
Matthew Garrett | mjg59@srcf.ucam.org
--
Matthew Garrett | mjg59@srcf.ucam.org
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-kernel@vger.kernel.org, linux-pm@lists.osdl.org
Subject: Userspace interface breakage in power/state
Date: Mon, 16 Jan 2006 00:27:03 +0000 [thread overview]
Message-ID: <20060116002703.GA4769@srcf.ucam.org> (raw)
(Resent, without the wrong address for lkml)
In older kernels, power/state for PCI devices took a PCI power state as
an argument and so "3" was an entirely sensible thing to echo into it.
In current kernels, it hits a BUG() in pci_choose_state and things blow
up.
While I realise that the former interface was broken and wrong, would it
be possible to move to a new one without breaking existing code?
--
Matthew Garrett | mjg59@srcf.ucam.org
--
Matthew Garrett | mjg59@srcf.ucam.org
next reply other threads:[~2006-01-16 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 0:27 Matthew Garrett [this message]
2006-01-16 0:27 ` Userspace interface breakage in power/state Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2006-01-16 0:25 Matthew Garrett
2006-01-16 19:20 ` Pavel Machek
2006-01-16 19:25 ` Matthew Garrett
2006-01-16 20:05 ` Pavel Machek
2006-01-16 20:22 ` Rafael J. Wysocki
2006-01-16 20:24 ` Pavel Machek
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=20060116002703.GA4769@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--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 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.