From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: linux-next: Tree for October 28
Date: Wed, 29 Oct 2008 09:21:56 +0100 [thread overview]
Message-ID: <20081029082156.GF17992@elte.hu> (raw)
In-Reply-To: <20081028162345.72b3180f.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Tue, 28 Oct 2008 16:00:45 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > > I have created today's linux-next tree at
> > > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> >
> > x86_64 allnoconfig:
> >
> > arch/x86/kernel/genx2apic_uv_x.c: In function 'uv_rtc_init':
> > arch/x86/kernel/genx2apic_uv_x.c:355: error: implicit declaration of function 'uv_bios_freq_base'
>
> oop, seems that this was caused by the presence of a stale
> include/asm-x86/uv/bios.h.
oh well, i just wasted half an hour trying to reproduce that build bug
on various trees :-/
but it wasnt a wasted effort: i found a deficiency in my allnoconfig
testing scripts.
Ingo
next prev parent reply other threads:[~2008-10-29 8:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 7:30 linux-next: Tree for October 28 Stephen Rothwell
2008-10-28 23:00 ` Andrew Morton
2008-10-28 23:23 ` Andrew Morton
2008-10-29 8:21 ` Ingo Molnar [this message]
2008-10-29 7:49 ` Ingo Molnar
2008-10-29 5:07 ` Andrew Morton
2008-10-29 12:01 ` Johannes Berg
2008-10-29 12:54 ` John W. Linville
2008-10-29 16:01 ` Greg KH
2008-10-29 21:39 ` Mark Fasheh
-- strict thread matches above, loose matches on Subject: below --
2009-10-28 8:06 Stephen Rothwell
2010-10-28 3:20 Stephen Rothwell
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=20081029082156.GF17992@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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