public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, linux-pm@osdl.org
Subject: Re: [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)
Date: Fri, 17 Feb 2006 21:09:00 -0800	[thread overview]
Message-ID: <20060217210900.514b5f4c.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.50.0602171757360.30811-100000@monsoon.he.net>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

Patrick Mochel <mochel@digitalimplant.org> wrote:
>
> 
> Signed-off-by: Patrick Mochel <mochel@linux.intel.com>
> 
> ---
> 
>  include/linux/pm.h |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> applies-to: 1ac50ba99ca37c65bdf3643c4056c246e401c18a
> 63b8e7f0896ce93834ac60c15df954b1e6d45e56
> diff --git a/include/linux/pm.h b/include/linux/pm.h
> index 5be87ba..a7324ea 100644
> --- a/include/linux/pm.h
> +++ b/include/linux/pm.h
> @@ -140,6 +140,7 @@ struct device;
> 
>  typedef struct pm_message {
>  	int event;
> +	u32 state;
>  } pm_message_t;

I don't quite understand.  This is a message which is sent to a driver
saying "go into this state", isn't it?

If so, what does the new `state' field tell us?


[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-02-18  5:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18  2:03 [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in) Patrick Mochel
2006-02-18  5:09 ` Andrew Morton [this message]
2006-02-18  5:45   ` Patrick Mochel
2006-02-18  6:10     ` Andrew Morton
2006-02-18  6:56       ` Patrick Mochel
2006-02-18 15:51 ` Pavel Machek
2006-02-18 20:15   ` [linux-pm] " Alan Stern
2006-02-19 23:57   ` Patrick Mochel

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=20060217210900.514b5f4c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=mochel@digitalimplant.org \
    --cc=torvalds@osdl.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