From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: bugme-admin@osdl.org, cpufreq@www.linux.org.uk
Subject: Re: New PowerManagement - cpufreq category?
Date: Mon, 16 Feb 2004 14:52:41 -0800 [thread overview]
Message-ID: <47480000.1076971961@flay> (raw)
In-Reply-To: <20040216185908.GA8531@dominikbrodowski.de>
--On Monday, February 16, 2004 19:59:08 +0100 Dominik Brodowski <linux@dominikbrodowski.de> wrote:
> On Mon, Feb 16, 2004 at 07:43:25AM -0800, Martin J. Bligh wrote:
>> --Dominik Brodowski <mail@dominikbrodowski.de> wrote (on Monday, February 16, 2004 09:14:12 +0100):
>>
>> > Quoting
>> > ------- Additional Comment #1 From Len Brown 2004-02-14 22:53 -------
>> > from bug #2081:
>> > "(we really should have a better category than power-management/other for
>> > cpufreq stuff)"
>> >
>> >
>> > What do you think about a new component "cpufreq" as part of
>> > "Power Management"?
>>
>> If it's a separated component that's receiving a fair number of bugs,
> Currently, the open bugs #2025, #2081, #1696 and #2111 would fall under this
> category. Maybe I missed some, though.
>
>> then yes we could. Who is the maintainer,
> Dave Jones <davej@redhat.com>
>
>> and where does it lie under the source tree?
> drivers/cpufreq/ and, for i386 [though other archs also support cpufreq]
> arch/i386/kernel/cpu/cpufreq/
I double-checked with davej ... now created and he owns it, thanks to Jon ;-)
prev parent reply other threads:[~2004-02-16 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 8:14 New PowerManagement - cpufreq category? Dominik Brodowski
2004-02-16 15:43 ` Martin J. Bligh
2004-02-16 18:59 ` Dominik Brodowski
2004-02-16 22:52 ` Martin J. Bligh [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=47480000.1076971961@flay \
--to=mbligh@aracnet.com \
--cc=bugme-admin@osdl.org \
--cc=cpufreq@www.linux.org.uk \
--cc=linux@dominikbrodowski.de \
/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.