From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc32: make sure we have an L3 before touch its control register
Date: Fri, 07 Oct 2005 10:26:48 +1000 [thread overview]
Message-ID: <1128644808.17365.2.camel@gaston> (raw)
In-Reply-To: <AFEB186E-99B9-4BE8-9AE3-315C74277483@freescale.com>
> Dope, you're right. I notice that we apparent do this for BTIC and
> DPM in this function though?
Yes, those bits are buggy. Good catch
Ben.
next prev parent reply other threads:[~2005-10-07 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 19:51 [PATCH] ppc32: make sure we have an L3 before touch its control register Kumar Gala
2005-09-24 22:10 ` Benjamin Herrenschmidt
2005-09-26 16:04 ` Kumar Gala
2005-10-07 0:26 ` Benjamin Herrenschmidt [this message]
2005-10-07 0:33 ` Benjamin Herrenschmidt
2005-10-07 14:39 ` Kumar Gala
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=1128644808.17365.2.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=kumar.gala@freescale.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).