public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ingo Molnar <mingo@elte•hu>, Jens Axboe <jens.axboe@oracle•com>
Cc: linux-next@vger•kernel.org, Eduardo Habkost <ehabkost@redhat•com>
Subject: linux-next: generic-ipi tree build failure
Date: Thu, 3 Jul 2008 17:38:06 +1000	[thread overview]
Message-ID: <20080703173806.c596ff13.sfr@canb.auug.org.au> (raw)

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

Hi Ingo, Jens,

Today's linux-next build (x86_64 allmodconfig) failed like this:

arch/x86/mm/init_64.c: In function 'set_pte_vaddr':
arch/x86/mm/init_64.c:153: error: 'pud_page' undeclared (first use in this function)
arch/x86/mm/init_64.c: At top level:
arch/x86/mm/init_64.c:188: error: redefinition of 'set_pte_vaddr'
arch/x86/mm/init_64.c:148: error: previous definition of 'set_pte_vaddr' was here

Caused by commit f2ff8984179fe447fc991c34718652e3079e6236 ("x86, 64-bit:
split set_pte_vaddr()") in combination with commit
c7f5cf4f8d53cbf0cf787c95221b34cd91794e4d ("manual merge of
generic-ipi-mergefixups").

I reverted the former commit which makes it build, but is probably not
correct.

-- 
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-07-03  7:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  7:38 Stephen Rothwell [this message]
2008-07-03  7:47 ` linux-next: generic-ipi tree build failure Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2008-07-03  7:10 Stephen Rothwell
2008-07-03  7:22 ` Jens Axboe
2008-07-03  7:26 ` Ingo Molnar

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=20080703173806.c596ff13.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=ehabkost@redhat$(echo .)com \
    --cc=jens.axboe@oracle$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    /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