From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: cpufreq tree build failure
Date: Tue, 20 Jan 2009 00:30:22 -0500 [thread overview]
Message-ID: <20090120053022.GB31797@redhat.com> (raw)
In-Reply-To: <20090120135059.6841cdc8.sfr@canb.auug.org.au>
On Tue, Jan 20, 2009 at 01:50:59PM +1100, Stephen Rothwell wrote:
> Hi Dave,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> arch/x86/kernel/cpu/cpufreq/powernow-k8.c: In function 'powernow_k8_cpu_init_acpi':
> arch/x86/kernel/cpu/cpufreq/powernow-k8.c:836: error: 'space_id' undeclared (first use in this function)
>
> Immediate cause is commit 77a33c31a78c6cd11395c8b554152be684110e94
> ("[CPUFREQ] checkpatch cleanups for powernow-k8") which clearly wasn't
> build tested.
wtf, I dropped a hunk somehow.
> I have dropped the cpufreq tree for today.
I regenerated the tree with the missing line.
Thanks for catching this.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2009-01-20 5:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 2:50 linux-next: cpufreq tree build failure Stephen Rothwell
2009-01-20 5:30 ` Dave Jones [this message]
2009-01-20 6:23 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 7:54 Stephen Rothwell
2009-02-05 9:33 ` Thomas Renninger
2009-02-05 9:47 ` Thomas Renninger
2009-02-05 17:45 ` Dave Jones
2009-02-05 20:57 ` Thomas Renninger
2009-02-05 21:34 ` Dave Jones
2009-02-24 6:21 Stephen Rothwell
2009-02-24 16:51 ` Dave Jones
2009-02-25 3:29 ` Stephen Rothwell
2009-02-25 3:45 ` Dave Jones
2009-02-25 4:23 ` Stephen Rothwell
2009-08-03 2:28 Stephen Rothwell
2009-08-03 23:22 ` Thomas Renninger
2009-08-03 23:44 ` Dave Jones
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=20090120053022.GB31797@redhat.com \
--to=davej@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.