From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 48721] acpi_cpufreq can't change CPU clock anymore
Date: Sat, 13 Oct 2012 02:29:44 +0000 (UTC) [thread overview]
Message-ID: <20121013022944.B5E3111FC39@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-48721-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=48721
--- Comment #2 from Maurizio Avogadro <mavoga@gmail.com> 2012-10-13 02:29:44 ---
Created an attachment (id=83151)
--> (https://bugzilla.kernel.org/attachment.cgi?id=83151)
3.6.1 kernel config
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-10-13 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 1:56 [Bug 48721] New: acpi_cpufreq can't change CPU clock anymore bugzilla-daemon
2012-10-13 1:57 ` [Bug 48721] " bugzilla-daemon
2012-10-13 2:03 ` bugzilla-daemon
2012-10-13 2:03 ` bugzilla-daemon
2012-10-13 2:08 ` bugzilla-daemon
2012-10-13 2:29 ` bugzilla-daemon [this message]
2012-10-13 7:17 ` bugzilla-daemon
2012-10-14 12:12 ` bugzilla-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=20121013022944.B5E3111FC39@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).