public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Mackerras <paulus@samba•org>, linuxppc-dev@ozlabs•org
Cc: linux-next@vger•kernel.org,
	Benjamin Herrenschmidt <benh@kernel•crashing.org>
Subject: linux-next: powerpc build failure
Date: Tue, 10 Jun 2008 16:54:41 +1000	[thread overview]
Message-ID: <20080610165441.a7c5ddd0.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 497 bytes --]

Hi Paul,

Today's linux-next tree build (powerpc ppc64_defconfig) failed like this:

  UPD     include/linux/compile.h
arch/powerpc/mm/built-in.o: In function `ht64_insert_pte':
hash_native_64.c:(.text+0x4756): undefined reference to `_PAGE_HPTE_SUB0'

I have reverted commit 2d9a973b0fee245af43b73412a08e88bc955644d
("powerpc: Free a PTE bit on ppc64 with 64K pages") for now.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-06-10  6:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  6:54 Stephen Rothwell [this message]
2008-06-10  7:20 ` linux-next: powerpc build failure Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2008-06-11  9:27 Stephen Rothwell
2008-06-11  9:59 ` Ingo Molnar
2008-06-12  1:38   ` Paul Mackerras
2008-06-12  5:33     ` Alan Modra
2008-06-12  7:05       ` Stephen Rothwell
2008-06-12  7:16         ` Ingo Molnar
2008-06-12  7:27           ` Stephen Rothwell
2008-06-12  7:47             ` Ingo Molnar
2008-06-12  7:23         ` Benjamin Herrenschmidt
2008-06-12  7:24         ` Stephen Rothwell
2008-06-12 18:12           ` Sam Ravnborg
2008-06-12  8:15         ` Alan Modra
2008-11-26 14:34 Stephen Rothwell
2008-11-26 23:16 ` Paul Mackerras
2008-11-27  0:26 ` Peter Teoh

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=20080610165441.a7c5ddd0.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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