From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Mackerras <paulus@samba•org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
linuxppc-dev@ozlabs•org
Cc: linux-next@vger•kernel.org, Kumar Gala <galak@kernel•crashing.org>
Subject: linux-next: scsi-post-merge tree build failure
Date: Tue, 23 Dec 2008 01:25:45 +1100 [thread overview]
Message-ID: <20081223012545.5b1e7f5e.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
Hi Paul, Ben,
Today's linux-next build (powerpc ppc44x_config) failed like this:
arch/powerpc/kvm/powerpc.c: In function 'kvm_arch_vcpu_put':
arch/powerpc/kvm/powerpc.c:333: error: implicit declaration of function '_tlbil_all'
Probably caused by commit 2a4aca1144394653269720ffbb5a325a77abd5fa
("powerpc/mm: Split low level tlb invalidate for nohash processors").
Reverting just that commit was too difficult, so I have reverted the
powerpc tree for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-12-22 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 14:25 Stephen Rothwell [this message]
2008-12-22 14:51 ` linux-next: scsi-post-merge tree build failure Stephen Rothwell
2008-12-22 20:56 ` Benjamin Herrenschmidt
2008-12-22 23:04 ` testing (Was: Re: linux-next: scsi-post-merge tree build failure) Stephen Rothwell
2008-12-23 0:19 ` Benjamin Herrenschmidt
2008-12-23 1:52 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2009-09-07 10:06 linux-next: scsi-post-merge tree build failure Stephen Rothwell
2009-09-08 8:12 ` Stephen Rothwell
2009-09-08 15:48 ` James Bottomley
2008-12-11 8:27 Stephen Rothwell
2008-12-11 8:28 ` Stephen Rothwell
2008-12-11 12:35 ` David Howells
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=20081223012545.5b1e7f5e.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=benh@kernel$(echo .)crashing.org \
--cc=galak@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