From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oliver@neukum.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
linux-pm@lists.linux-foundation.org,
Alexey Starikovskiy <astarikovskiy@suse.de>,
Johannes Berg <johannes@sipsolutions.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [RFC][PATCH] PM: Introduce new top level suspend and hibernation callbacks (rev. 2)
Date: Wed, 26 Mar 2008 21:46:38 +0100 [thread overview]
Message-ID: <200803262146.39899.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0803261236080.7344-100000@iolanthe.rowland.org>
On Wednesday, 26 of March 2008, Alan Stern wrote:
> On Wed, 26 Mar 2008, Oliver Neukum wrote:
>
> > Am Mittwoch, 26. März 2008 15:40:27 schrieb Alan Stern:
> > > Remember, the whole purpose of this is to let drivers know when the
> > > system is going to sleep or waking up. Proper handling of devices is
> > > up to the drivers, not up to the core.
> >
> > Then declare these methods void. We cannot introduce methods that deliberately
> > ignore errors. Reporting is also better done in the drivers.
>
> That decision is up to Rafael. Changing the methods to return void is
> okay with me.
But that's not what they currently do, either.
If I change the methods to void and it turns out in the future that it's
better if they return error codes, it will be rather difficult to go back and
change everything. For this reason, I'd prefer to retain the returning of
error codes.
What exactly do you whink would be wrong with using the error codes to avoid
resuming the children of devices that failed to resume?
Rafael
next prev parent reply other threads:[~2008-03-26 20:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 0:01 [RFC][PATCH] PM: Introduce new top level suspend and hibernation callbacks (rev. 2) Rafael J. Wysocki
2008-03-21 0:21 ` [linux-pm] " Johannes Berg
2008-03-21 0:26 ` Rafael J. Wysocki
2008-03-25 9:49 ` Oliver Neukum
2008-03-25 13:06 ` Rafael J. Wysocki
2008-03-25 13:15 ` Oliver Neukum
2008-03-25 14:19 ` Alan Stern
2008-03-25 14:24 ` Oliver Neukum
2008-03-25 14:33 ` Alan Stern
2008-03-25 19:48 ` Oliver Neukum
2008-03-25 20:41 ` Rafael J. Wysocki
2008-03-25 20:49 ` Oliver Neukum
2008-03-25 20:56 ` Rafael J. Wysocki
2008-03-26 14:10 ` Alan Stern
2008-03-26 14:24 ` Oliver Neukum
2008-03-26 14:40 ` Alan Stern
2008-03-26 15:42 ` Oliver Neukum
2008-03-26 16:36 ` Alan Stern
2008-03-26 20:46 ` Rafael J. Wysocki [this message]
2008-03-27 2:48 ` Alan Stern
2008-03-21 1:21 ` Alan Stern
2008-03-21 2:14 ` Rafael J. Wysocki
2008-03-21 2:53 ` Alan Stern
2008-03-22 22:17 ` Rafael J. Wysocki
2008-03-22 23:28 ` Alan Stern
2008-03-22 23:44 ` Rafael J. Wysocki
2008-03-23 2:07 ` Alan Stern
2008-03-23 18:41 ` Rafael J. Wysocki
2008-03-21 8:15 ` Sam Ravnborg
2008-03-23 21:16 ` 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=200803262146.39899.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=astarikovskiy@suse.de \
--cc=johannes@sipsolutions.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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