From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Meelis Roos <mroos@linux.ee>
Cc: linuxppc-dev@ozlabs.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ppc compile failure (__flush_icache_range etc undeclared)
Date: Sat, 10 May 2008 08:22:46 -0500 [thread overview]
Message-ID: <20080510082246.0ce82981@zod.rchland.ibm.com> (raw)
In-Reply-To: <Pine.SOC.4.64.0805101448580.8450@math.ut.ee>
On Sat, 10 May 2008 14:51:27 +0300 (EEST)
Meelis Roos <mroos@linux.ee> wrote:
> Tried 2.6.26-rc1+git on ppc (arch/ppc, PReP subarch) and got this:
Segher sent patches to fix this earlier this week. You can find them
here:
http://patchwork.ozlabs.org/linuxppc/patch?id=18348
http://patchwork.ozlabs.org/linuxppc/patch?id=18346
http://patchwork.ozlabs.org/linuxppc/patch?id=18347
People keep breaking arch/ppc and it seems there's little motivation to
fix it since it's going away in a month.
josh
next prev parent reply other threads:[~2008-05-10 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 11:51 ppc compile failure (__flush_icache_range etc undeclared) Meelis Roos
2008-05-10 13:22 ` Josh Boyer [this message]
2008-05-10 13:26 ` Segher Boessenkool
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=20080510082246.0ce82981@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mroos@linux.ee \
/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).