From: David Brownell <david-b@pacbell.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] s2ram: add arch irq disable/enable hooks
Date: Tue, 24 Apr 2007 20:45:56 -0700 [thread overview]
Message-ID: <200704242045.56409.david-b@pacbell.net> (raw)
In-Reply-To: <20070424181615.GB15920@elf.ucw.cz>
On Tuesday 24 April 2007, Pavel Machek wrote:
> Hi!
>
> > > > This is a very straightforward point. A function that's
> > > > called on non-S2RAM paths shouldn't be named as if it's
> > > > only for S2RAM.
> > >
> > > And the function that's called for s2ram+standby should not be named
> > > as if it's also for swsusp...
> > >
> > > > Ergo, those two functions are misnamed. End of story.
> > >
> > > ...which is not only misnamed, it is also actively confusing. (And
> > > someone _will_ ask me to call that function from swsusp, too.
> > >
> > > ...maybe we could solve it with a big fat comment?
> >
> > So how about we don't call them s2ram which is confusing since s2ram is
> > only one suspend state we support but call them suspend as David
> > originally proposed and add a comment that since suspend-to-disk isn't a
> > true suspend state, they are not called there?
>
> calling them ..._suspend_... and explaining in comment is probably ok.
Yah, I'm fine with that too.
> > Has anybody figured out if (and if yes, where) we should add them to
> > some header file?
>
> include/linux/pm.h is probably the right place.
>
> Feel free to add my acked-by: and send it to akpm.
> 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-25 3: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
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 [this message]
-- 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=200704242045.56409.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
/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.