All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: Tree for October 28
Date: Tue, 28 Oct 2008 16:00:45 -0700	[thread overview]
Message-ID: <20081028160045.2a890509.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081028183055.fbcf5420.sfr@canb.auug.org.au>

On Tue, 28 Oct 2008 18:30:55 +1100
Stephen Rothwell <sfr@canb.auug.org.au> 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'
arch/x86/kernel/genx2apic_uv_x.c: In function 'uv_system_init':
arch/x86/kernel/genx2apic_uv_x.c:438: error: implicit declaration of function 'uv_bios_init'
arch/x86/kernel/genx2apic_uv_x.c:439: error: implicit declaration of function 'uv_bios_get_sn_info'
arch/x86/kernel/genx2apic_uv_x.c:439: error: 'uv_type' undeclared (first use in this function)
arch/x86/kernel/genx2apic_uv_x.c:439: error: (Each undeclared identifier is reported only once
arch/x86/kernel/genx2apic_uv_x.c:439: error: for each function it appears in.)
arch/x86/kernel/genx2apic_uv_x.c:439: error: 'sn_partition_id' undeclared (first use in this function)
arch/x86/kernel/genx2apic_uv_x.c:440: error: 'uv_coherency_id' undeclared (first use in this function)
arch/x86/kernel/genx2apic_uv_x.c:440: error: 'uv_region_size' undeclared (first use in this function)
make[1]: *** [arch/x86/kernel/genx2apic_uv_x.o] Error 1
make: *** [arch/x86/kernel/genx2apic_uv_x.o] Error 2


Guys, allnoconfig breakage is very common.  It's easy to configure and
is very quick to test.  Please use it.

  reply	other threads:[~2008-10-28 23:01 UTC|newest]

Thread overview: 18+ 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 [this message]
2008-10-28 23:23   ` Andrew Morton
2008-10-29  8:21     ` Ingo Molnar
2008-10-29  7:49   ` Ingo Molnar
2008-10-29  5:07 ` Andrew Morton
2008-10-29  5:07   ` Andrew Morton
2008-10-29 12:01   ` Johannes Berg
2008-10-29 12:01     ` Johannes Berg
2008-10-29 12:54   ` John W. Linville
2008-10-29 12:54     ` John W. Linville
2008-10-29 16:01     ` Greg KH
2008-10-29 16:01       ` Greg KH
2008-10-29 21:39   ` Mark Fasheh
2008-10-29 21:39     ` Mark Fasheh
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=20081028160045.2a890509.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.