From: Pavel Machek <pavel@ucw.cz>
To: David Brownell <david-b@pacbell.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-pm@lists.linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] s2ram: add arch irq disable/enable hooks
Date: Sat, 21 Apr 2007 23:45:57 +0200 [thread overview]
Message-ID: <20070421214557.GB2758@elf.ucw.cz> (raw)
In-Reply-To: <200704211006.58857.david-b@pacbell.net>
Hi!
> > > Or maybe arch_suspend_disable_irqs() ... there are PM
> > > operations that don't involve system suspend states.
> >
> > Yeah, probably better and I'm fine with that, but the crowd who screamed
> > when I noted that CONFIG_SOFTWARE_SUSPEND had nothing to do with suspend
> > states might be confused... It should be obvious that this isn't called
> > for suspend to disk.
>
> Yeah, but SOFTWARE_SUSPEND is also a misnomer. It's more of a
Well, that's the way it is. "suspend" == s2ram, standby, swsusp,
swsusp+S4 in kernel context.
> system checkpoint/restore framework. And even userspace makes
> that distinction clear, calling it "Hibernate" not "Suspend".
Gnome deciding to confuse their users is _their_ problem.
> I feel a Kconfig patch coming on ... ;)
I do not think confusion from a change is worth the benefit.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-04-21 21:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 11:00 [PATCH] s2ram: add arch irq disable/enable hooks Johannes Berg
2007-04-19 21:55 ` Andrew Morton
2007-04-20 15:34 ` Johannes Berg
2007-04-20 6:57 ` Greg KH
2007-04-20 15:31 ` Johannes Berg
2007-04-20 17:39 ` Greg KH
2007-04-20 19:37 ` Johannes Berg
2007-04-20 19:44 ` Andrew Morton
2007-04-20 19:51 ` Johannes Berg
2007-04-20 20:36 ` Rafael J. Wysocki
2007-04-20 20:51 ` Johannes Berg
2007-04-20 21:08 ` Rafael J. Wysocki
2007-04-21 13:57 ` Johannes Berg
2007-04-21 14:07 ` Pavel Machek
2007-04-21 15:41 ` David Brownell
2007-04-21 16:16 ` Johannes Berg
2007-04-21 16:55 ` David Brownell
2007-04-21 17:01 ` Johannes Berg
2007-04-21 17:06 ` David Brownell
2007-04-21 17:49 ` Johannes Berg
2007-04-21 21:47 ` Pavel Machek
2007-04-21 22:04 ` Johannes Berg
2007-04-21 21:45 ` Pavel Machek [this message]
2007-04-22 3:10 ` David Brownell
2007-04-22 13:09 ` Pavel Machek
2007-04-26 11:02 ` David Woodhouse
2007-04-21 21:44 ` Pavel Machek
2007-04-22 3:05 ` David Brownell
2007-04-22 13:13 ` Pavel Machek
2007-04-24 13:51 ` Johannes Berg
2007-04-24 18:16 ` Pavel Machek
2007-04-25 3:45 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 21:54 [PATCH] pm_ops: add irq enable/disable hooks Johannes Berg
2007-04-17 17:18 ` [PATCH] s2ram: add arch irq disable/enable hooks Johannes Berg
2007-04-18 11:27 ` 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=20070421214557.GB2758@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.linux-foundation.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