From: David Brownell <david-b@pacbell.net>
To: Preece Scott-PREECE <scott.preece@motorola.com>
Cc: linux-pm@lists.osdl.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: RE: on-ness
Date: Fri, 21 Apr 2006 11:15:31 -0700 [thread overview]
Message-ID: <200604211115.31687.david-b@pacbell.net> (raw)
In-Reply-To: <ADE4D9DBCFC3A345AAA95C195F62B6DD0137BC0B@de01exm64.ds.mot.com>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
On Friday 21 April 2006 10:58 am, Preece Scott-PREECE wrote:
> However, I also have to admit that I like the notion of the zero-state
> meaning having a consistent meaning across the different atttributes and
> it might be good to have a similarly consistent name for the
> maximum/full-operation state across the attributes...
Well, not "zero-state" since that implies numbering. But sure,
maybe that's what "on" should mean ... for CPUs, devices, systems.
- Dave
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-04-21 18:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 17:58 RE: on-ness Preece Scott-PREECE
2006-04-21 18:15 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-27 14:12 Scott E. Preece
2006-04-27 17:01 ` Patrick Mochel
2006-05-01 21:58 ` David Brownell
2006-04-24 21:32 Woodruff, Richard
2006-04-27 1:39 ` Patrick Mochel
2006-05-01 21:35 ` David Brownell
2006-04-18 18:39 Brown, Len
2006-04-20 13:25 ` Pavel Machek
2006-04-21 15:27 ` David Brownell
2006-04-21 15:40 ` Dominik Brodowski
2006-04-21 17:03 ` David Brownell
2006-04-21 17:12 ` Dominik Brodowski
2006-04-21 18:30 ` David Brownell
2006-04-21 18:33 ` Dominik Brodowski
2006-04-21 19:00 ` David Brownell
2006-04-21 19:01 ` Pavel Machek
2006-04-24 21:04 ` David Brownell
2006-04-24 21:32 ` Pavel Machek
2006-04-24 23:21 ` David Brownell
2006-04-21 17:15 ` David Brownell
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=200604211115.31687.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=scott.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox