From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Joseph Fannin <jfannin@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: BUG() in current git, __dma_alloc_coherent, Beige G3
Date: Mon, 16 Jun 2008 19:05:28 +1000 [thread overview]
Message-ID: <1213607128.8129.129.camel@pasglop> (raw)
In-Reply-To: <20080616073041.GA26917@nineveh.local>
On Mon, 2008-06-16 at 03:30 -0400, Joseph Fannin wrote:
> I think it's because PPC_PRPMC2800 and MPC5121_ADS both live under
> PPC_MULTIPLATFORM, and end up selecting NOT_COHERENT_CACHE.
>
> If the button in Kconfig isn't labeled "Do Not Push", heck, I'll build
> it.
Heh, ok, disable those then.
Cheers,
Ben.
prev parent reply other threads:[~2008-06-16 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 1:46 BUG() in current git, __dma_alloc_coherent, Beige G3 Joseph Fannin
2008-06-16 4:50 ` Benjamin Herrenschmidt
2008-06-16 7:03 ` Gerhard Pircher
2008-06-16 7:11 ` Benjamin Herrenschmidt
2008-06-16 7:30 ` Joseph Fannin
2008-06-16 9:05 ` 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=1213607128.8129.129.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jfannin@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
/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).