From: lucke <lucke@o2.pl>
To: cpufreq@lists.linux.org.uk
Subject: Re: cpufreq and suspend
Date: Sun, 24 Sep 2006 18:32:51 +0200 [thread overview]
Message-ID: <200609241832.51705.lucke@o2.pl> (raw)
>> For completeness, MB is Asus A8N-E with latest BIOS.
>Okay, I'll go try to dig one of those up.
Any success in obtaining this MB, Mark?
If you fail to get one, is there perhaps anything I could do to help you debug
this issue?
Regards,
Luke
next reply other threads:[~2006-09-24 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 16:32 lucke [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-20 18:44 cpufreq and suspend lucke
2006-09-20 18:53 ` Langsdorf, Mark
2006-09-20 21:09 ` lucke
2006-09-20 21:32 ` Langsdorf, Mark
2006-09-15 20:25 lucke
2006-09-15 20:42 ` Langsdorf, Mark
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=200609241832.51705.lucke@o2.pl \
--to=lucke@o2.pl \
--cc=cpufreq@lists.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.