From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 6303] Fujitsu-Siemens P4 Amilo D 7830 laptop has no govenors with 2.6.16
Date: Thu, 3 Aug 2006 16:10:29 -0700 [thread overview]
Message-ID: <200608032310.k73NATvZ010200@fire-2.osdl.org> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=6303
bunk@stusta.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bunk@stusta.de
Status|NEW |CLOSED
Resolution| |PATCH_ALREADY_AVAILABLE
------- Additional Comments From bunk@stusta.de 2006-08-03 16:05 -------
Please reopen this bug if it is still present in kernel 2.6.17.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2006-08-03 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 23:10 bugme-daemon [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-14 21:50 [Bug 6303] Fujitsu-Siemens P4 Amilo D 7830 laptop has no govenors with 2.6.16 bugme-daemon
2006-04-08 23:19 bugme-daemon
2006-03-29 21:59 bugme-daemon
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=200608032310.k73NATvZ010200@fire-2.osdl.org \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/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.