From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
Date: Fri, 22 Mar 2013 14:13:44 +0000 (UTC) [thread overview]
Message-ID: <20130322141344.3FD4F11FB81@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55411-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=55411
--- Comment #27 from Borislav Petkov <bp@alien8.de> 2013-03-22 14:13:44 ---
On Fri, Mar 22, 2013 at 07:40:45PM +0530, Viresh Kumar wrote:
> acpi-cpufreq is broken and so all others who are using it. Sorry for
> asking the stupid question now but what's the hierarchy of cpufreq
> drivers for intel (I will try to go through it now), some drivers use
> acpi-cpufreq driver?
All relevant x86 out there uses acpi-cpufreq. Which means that breaking
it, breaks cpufreq on x86. Which is absolutely a no-no.
--
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:[~2013-03-22 14:13 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 9:13 [Bug 55411] New: sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram bugzilla-daemon
2013-03-18 9:21 ` [Bug 55411] " bugzilla-daemon
2013-03-18 9:26 ` bugzilla-daemon
2013-03-18 9:27 ` bugzilla-daemon
2013-03-18 9:38 ` bugzilla-daemon
2013-03-18 9:39 ` bugzilla-daemon
2013-03-18 9:56 ` bugzilla-daemon
2013-03-18 10:40 ` bugzilla-daemon
2013-03-18 11:53 ` bugzilla-daemon
2013-03-18 12:14 ` bugzilla-daemon
2013-03-19 6:16 ` bugzilla-daemon
2013-03-19 7:49 ` bugzilla-daemon
2013-03-19 7:57 ` bugzilla-daemon
2013-03-19 8:23 ` bugzilla-daemon
2013-03-19 8:27 ` bugzilla-daemon
2013-03-19 8:50 ` bugzilla-daemon
2013-03-22 12:10 ` bugzilla-daemon
2013-03-22 12:15 ` bugzilla-daemon
2013-03-22 12:53 ` bugzilla-daemon
2013-03-22 13:05 ` bugzilla-daemon
2013-03-22 13:21 ` bugzilla-daemon
2013-03-22 13:43 ` bugzilla-daemon
2013-03-22 14:03 ` Rafael J. Wysocki
2013-03-22 14:06 ` Viresh Kumar
2013-03-22 13:54 ` bugzilla-daemon
2013-03-22 13:56 ` bugzilla-daemon
2013-03-22 14:04 ` bugzilla-daemon
2013-03-22 14:05 ` bugzilla-daemon
2013-03-22 14:06 ` bugzilla-daemon
2013-03-22 14:10 ` bugzilla-daemon
2013-03-22 14:11 ` bugzilla-daemon
2013-03-22 14:13 ` bugzilla-daemon [this message]
2013-03-23 18:35 ` bugzilla-daemon
2013-03-24 9:05 ` bugzilla-daemon
2013-03-24 9:10 ` bugzilla-daemon
2013-03-24 9:48 ` bugzilla-daemon
2013-03-24 10:02 ` bugzilla-daemon
2013-03-24 10:31 ` bugzilla-daemon
2013-03-24 11:49 ` bugzilla-daemon
2013-03-24 12:16 ` bugzilla-daemon
2013-03-24 12:23 ` bugzilla-daemon
2013-03-25 11:15 ` bugzilla-daemon
2013-03-25 11:23 ` bugzilla-daemon
2013-03-25 13:55 ` bugzilla-daemon
2013-03-29 14:14 ` bugzilla-daemon
2013-04-13 17:45 ` bugzilla-daemon
[not found] <bug-55411-70601@https.bugzilla.kernel.org/>
[not found] ` <20130319074953.C200811FB80@bugzilla.kernel.org>
2013-03-19 8:50 ` Viresh Kumar
2013-03-22 12:17 ` Rafael J. Wysocki
2013-03-22 12:15 ` Viresh Kumar
2013-03-22 13:12 ` Rafael J. Wysocki
2013-03-22 13:21 ` Borislav Petkov
2013-03-22 12:53 ` Thomas Renninger
2013-03-22 13:43 ` Viresh Kumar
2013-03-22 13:54 ` Borislav Petkov
2013-03-22 14:05 ` Viresh Kumar
2013-03-22 14:11 ` Borislav Petkov
2013-03-22 14:04 ` Thomas Renninger
2013-03-22 14:10 ` Viresh Kumar
2013-03-22 14:13 ` Borislav Petkov
2013-03-24 9:05 ` Thomas Renninger
2013-03-24 9:10 ` Viresh Kumar
2013-03-24 10:02 ` Viresh Kumar
2013-03-24 11:49 ` Duncan
2013-03-24 12:16 ` Viresh Kumar
2013-03-24 12:23 ` Viresh Kumar
2013-03-25 11:15 ` Duncan
2013-03-25 11:23 ` Viresh Kumar
2013-03-25 13:55 ` Borislav Petkov
2013-03-29 14:14 ` Viresh Kumar
2013-03-24 10:31 ` Borislav Petkov
2013-03-23 18:35 ` Viresh Kumar
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=20130322141344.3FD4F11FB81@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 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.