From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Building current git for 405 is broken
Date: Thu, 08 Jan 2009 08:13:09 +1100 [thread overview]
Message-ID: <1231362789.2142.23.camel@pasglop> (raw)
In-Reply-To: <200901071510.45923.matthias.fuchs@esd-electronics.com>
On Wed, 2009-01-07 at 15:10 +0100, Matthias Fuchs wrote:
> Hi Benjamin,
>
> commit 2a4aca114439 (powerpc/mm: Split low level tlb invalidate for nohash processors)
> breaks building for 40x CPUs. This is what I get when building for the walnut board:
The fix is in my tree, I'll push it out and ask Linus to pull later
today or tomorrow.
Cheers,
Ben.
prev parent reply other threads:[~2009-01-07 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 14:10 Building current git for 405 is broken Matthias Fuchs
2009-01-07 14:36 ` Josh Boyer
2009-01-07 14:37 ` Kumar Gala
2009-01-07 21:13 ` Benjamin Herrenschmidt [this message]
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=1231362789.2142.23.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matthias.fuchs@esd-electronics.com \
/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;
as well as URLs for NNTP newsgroup(s).