From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Alexey Starikovskiy <astarikovskiy@suse.de>
Subject: Re: [RFC] Add extra PM_EVENT_* codes for use by subsystems
Date: Sun, 2 Mar 2008 19:16:12 +0100 [thread overview]
Message-ID: <200803021916.13041.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0803021017280.9430-100000@netrider.rowland.org>
On Sunday, 2 of March 2008, Alan Stern wrote:
> On Sun, 2 Mar 2008, Rafael J. Wysocki wrote:
>
> > On Friday, 29 of February 2008, Alan Stern wrote:
> > > Is there any objection to adding extra PM_EVENT_* codes? Although they
> > > won't ever be issued by the PM core, they will come in handy for
> > > internal uses in power-aware subsystems (like USB).
> >
> > Well, this is in a (slight) conflict with the hibernation/suspend callbacks
> > rework that I'm working on with Alex. I'll send the first patch in a few
> > minutes for comments.
>
> If you want to add my new codes to yours, that would be fine. Or I
> could wait until after your new callbacks are merged before submitting
> the new event codes. Whatever you think is best.
That should be two different patches, I think.
If you could wait for the new callbacks, that would be better from my
standpoint (we may decide to add some more callbacks and therefore
some more PM_EVENT_* codes, for example).
Thanks,
Rafael
prev parent reply other threads:[~2008-03-02 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 17:27 [RFC] Add extra PM_EVENT_* codes for use by subsystems Alan Stern
2008-03-01 11:47 ` Pavel Machek
2008-03-02 12:57 ` Rafael J. Wysocki
2008-03-02 15:18 ` Alan Stern
2008-03-02 18:16 ` Rafael J. Wysocki [this message]
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=200803021916.13041.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=astarikovskiy@suse.de \
--cc=linux-pm@lists.linux-foundation.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