From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: Dominik Brodowski
<linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Robert Moore
<robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Subject: Re: Re: [PATCHES] add _CST support
Date: 27 Dec 2004 22:27:15 -0500 [thread overview]
Message-ID: <1104204434.18166.50.camel@d845pe> (raw)
In-Reply-To: <20041223130723.GE731-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
On Thu, 2004-12-23 at 08:07, Pavel Machek wrote:
> > C-states are enumerated C0...Cn
> > C-state types are enumerated C1, C2, C3.
> > I don't see any confusion in the name-space duplicates
> > as long as you know you're talking about C-states or C-state-types.
> >
>
> Unfortunately, people often don't know what they are talking about.
> Having two things called C2 is definitely going to confuse just
> about everyone but you...
Probably we should not mess with the "well known" (hah;-) name space for
C-states themselves (C0...Cn).
Types, on the other hand, would probably be well addressed with a enum
whose vales are 1,2,3 so if we chose to print them out they'd simply be
a %d -- using C%d only for actual C-states themselves.
would that be better?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-28 3:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 21:51 [PATCHES] add _CST support Dominik Brodowski
[not found] ` <20041127215118.GA30309-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-11-27 21:56 ` Dominik Brodowski
2004-12-22 5:44 ` Len Brown
2004-12-23 0:08 ` Dominik Brodowski
[not found] ` <20041223000842.GA8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23 5:02 ` Len Brown
2004-12-23 13:07 ` Pavel Machek
[not found] ` <20041223130723.GE731-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-12-28 3:27 ` Len Brown [this message]
2004-12-28 17:50 ` Dominik Brodowski
2004-12-28 21:28 ` Pavel Machek
2004-12-22 6:52 ` Len Brown
2004-12-22 20:37 ` Len Brown
2004-12-23 0:18 ` Dominik Brodowski
[not found] ` <20041223001830.GC8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23 5:30 ` Len Brown
2004-12-23 0:10 ` Dominik Brodowski
[not found] ` <20041223001024.GB8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23 5:07 ` Len Brown
2004-12-22 7:22 ` Len Brown
2004-12-22 20:13 ` Len Brown
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=1104204434.18166.50.camel@d845pe \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
--cc=linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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