From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Nigel Cunningham <nigel@nigel.suspend2.net>,
Pavel Machek <pavel@ucw.cz>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] swsusp: Do not use pm_ops
Date: Thu, 3 May 2007 11:52:38 +0200 [thread overview]
Message-ID: <200705031152.38933.rjw@sisk.pl> (raw)
In-Reply-To: <1178185551.13233.85.camel@johannes.berg>
On Thursday, 3 May 2007 11:45, Johannes Berg wrote:
> On Thu, 2007-05-03 at 11:46 +0200, Rafael J. Wysocki wrote:
>
> > Well, BUG_ON() is extremely user-unfriendly, and it'd trigger even if the user
> > actually didn't intend to suspend at all.
>
> Well, hibernation_set_ops is invoked whenever the user loads his ACPI
> module with S4 possible, and typically having a BUG_ON here will make
> the developers who wrote the code that calls hibernation_set_ops see it
> right away while they might miss the message.
>
> I don't care much though, it just seems wasteful to have this string in
> there when it'll never be seen by anyone but the developers who create
> new hibernation_ops.
You're making the dangerous assumption that all patches get tested before
hitting users. ;-)
Greetings,
Rafael
next prev parent reply other threads:[~2007-05-03 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 20:13 [PATCH] swsusp: Do not use pm_ops Rafael J. Wysocki
2007-05-03 8:41 ` Johannes Berg
2007-05-03 9:46 ` Rafael J. Wysocki
2007-05-03 9:45 ` Johannes Berg
2007-05-03 9:52 ` Rafael J. Wysocki [this message]
2007-05-03 10:11 ` Pavel Machek
2007-05-03 10:18 ` Rafael J. Wysocki
2007-05-03 10:31 ` Nigel Cunningham
2007-05-03 12:12 ` Johannes Berg
2007-05-03 12:53 ` Rafael J. Wysocki
2007-05-03 12:13 ` Johannes Berg
2007-05-03 12:54 ` 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=200705031152.38933.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=johannes@sipsolutions.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=penberg@cs.helsinki.fi \
/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