From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Dave Jones <davej@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Mark Langsdorf <mark.langsdorf@amd.com>
Subject: Re: CPUFreq compilation failure with current GIT.
Date: Fri, 13 Jul 2007 16:29:18 +1000 [thread overview]
Message-ID: <200707131629.20063.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <20070713045346.GA28641@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
Hi Dave et al.
On Friday 13 July 2007 14:53:46 Dave Jones wrote:
> On Fri, Jul 13, 2007 at 01:23:16PM +1000, Nigel Cunningham wrote:
> Fixed in cpufreq.git, will go to linus real soon.
> patch below..
Thanks!
Nigel
--
See http://www.tuxonice.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-07-13 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 3:23 CPUFreq compilation failure with current GIT Nigel Cunningham
2007-07-13 4:53 ` Dave Jones
2007-07-13 6:29 ` Nigel Cunningham [this message]
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=200707131629.20063.nigel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=nigel@suspend2.net \
/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