From: Greg KH <greg@kroah.com>
To: "Scott E. Preece" <preece@motorola.com>
Cc: daviado@gmail.com, linux-pm@lists.osdl.org,
dsingleton@mvista.com, pavel@ucw.cz
Subject: Re: PowerOp Design and working patch
Date: Mon, 7 Aug 2006 09:58:41 -0700 [thread overview]
Message-ID: <20060807165841.GB6849@kroah.com> (raw)
In-Reply-To: <200608071412.k77ECEQD009852@olwen.urbana.css.mot.com>
A: No.
Q: Should I include quotations after my reply?
On Mon, Aug 07, 2006 at 09:12:14AM -0500, Scott E. Preece wrote:
>
> While I think it makes sense to treat a list as a "single value" in this
> kind of case
A simple list, like what we have today in /sys/power/state, yes. But
with paramater information? no.
>, a reasonable alternative would be to make /sys/power/supported_states
>a directory, with separate files for each supported OP.
Sure, if you want to do that, fine. But then you are looking a lot like
configfs :)
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-07 16:58 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 14:12 PowerOp Design and working patch Scott E. Preece
2006-08-07 16:58 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-08 13:54 Scott E. Preece
2006-08-08 16:49 ` Tim Bird
2006-08-08 13:44 Scott E. Preece
2006-08-08 13:52 ` Pavel Machek
2006-08-08 15:53 ` Matthew Locke
2006-08-08 16:03 ` Matthew Locke
2006-08-08 18:10 ` Igor Stoppa
2006-08-01 10:09 Matthew Locke
2006-07-28 22:31 david singleton
2006-07-28 23:38 ` Greg KH
2006-07-29 0:26 ` david singleton
2006-07-29 0:38 ` david singleton
2006-07-29 0:45 ` Greg KH
2006-07-29 5:12 ` david singleton
2006-07-29 19:07 ` Eugeny S. Mints
2006-07-30 4:43 ` david singleton
2006-07-30 11:02 ` Vitaly Wool
2006-08-01 0:59 ` david singleton
2006-08-01 10:09 ` Matthew Locke
2006-08-01 10:22 ` Matthew Locke
2006-08-01 18:31 ` david singleton
2006-08-01 18:52 ` Tim Bird
2006-08-01 18:59 ` david singleton
2006-08-01 19:17 ` Vitaly Wool
2006-08-01 19:28 ` Vitaly Wool
2006-08-06 22:11 ` Pavel Machek
2006-08-07 10:34 ` Igor Stoppa
2006-08-07 19:45 ` Tim Bird
2006-08-08 10:07 ` Pavel Machek
2006-08-08 11:12 ` Igor Stoppa
2006-08-08 11:33 ` Pavel Machek
2006-08-08 16:43 ` Tim Bird
2006-08-01 12:23 ` Vitaly Wool
2006-08-01 18:25 ` Tim Bird
2006-08-01 18:02 ` Tim Bird
2006-08-06 22:05 ` Pavel Machek
2006-08-07 3:52 ` david singleton
2006-08-07 4:17 ` Greg KH
2006-08-07 4:32 ` Vitaly Wool
2006-07-29 22:09 ` Greg KH
2006-08-01 0:36 ` david singleton
2006-08-01 1:27 ` david singleton
2006-08-07 22:06 ` 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=20060807165841.GB6849@kroah.com \
--to=greg@kroah.com \
--cc=daviado@gmail.com \
--cc=dsingleton@mvista.com \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=preece@motorola.com \
/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.