From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 8581] acpi-cpufreq gets very confused on suspend to ram
Date: Sun, 21 Oct 2007 17:24:23 -0700 (PDT) [thread overview]
Message-ID: <20071022002423.3FC91108014@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-8581-3570@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=8581
davej@codemonkey.org.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|cpufreq@www.linux.org.uk |davej@codemonkey.org.uk
Status|NEW |ASSIGNED
------- Comment #8 from davej@codemonkey.org.uk 2007-10-21 17:24 -------
there's some whitespace damage in this patch (spaces instead of tabs).
Asides from that though, it looks like the right thing to do.
Can you fix that up, and bounce a copy to cpufreq@www.linux.org.uk please?
Thanks.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-10-22 0:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8581-3570@http.bugzilla.kernel.org/>
2007-08-08 17:04 ` [Bug 8581] acpi-cpufreq gets very confused on suspend to ram bugme-daemon
2007-09-23 12:26 ` bugme-daemon
2007-10-06 15:38 ` bugme-daemon
2007-10-08 13:47 ` bugme-daemon
2007-10-12 19:48 ` bugme-daemon
2007-10-21 13:13 ` bugme-daemon
2007-10-22 0:24 ` bugme-daemon [this message]
2007-10-22 7:50 ` Elias Oltmanns
2007-10-22 20:49 ` Dave Jones
2007-06-04 16:45 bugme-daemon
-- strict thread matches above, loose matches on Subject: below --
2007-06-04 12:38 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=20071022002423.3FC91108014@picon.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox