From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Joshua Williams <joshua.williams@qlogic.com>
Subject: Re: [PATCH] Various new ibm405 DCRN #defines
Date: Wed, 23 Jan 2008 07:58:48 +1100 [thread overview]
Message-ID: <1201035528.6807.34.camel@pasglop> (raw)
In-Reply-To: <20080122111038.1072dac4@weaponx>
On Tue, 2008-01-22 at 11:10 -0600, Josh Boyer wrote:
> On Tue, 22 Jan 2008 11:08:38 -0600
> Joshua Williams <joshua.williams@qlogic.com> wrote:
>
> > Benjamin Herrenschmidt wrote:
> > > On Mon, 2008-01-21 at 16:43 -0600, Joshua Williams wrote:
> > >> Various new ibm405 DCRN #defines.
> > >>
> > >> Signed-off-by: Joshua Williams <joshua.williams@qlogic.com>
> > >
> > > May I ask what for ? :-) Also, it's all arch/ppc, not arch/powerpc...
> > > nothing we want to improve to much on at this stage unless there's a
> > > really good reason.
> >
> > The 405x #defines were incomplete and this was meant to
> > make them a bit tighter. Since arch/ppc is in life support
> > mode this can wait until the 405x stuff gets moved over to
> > arch/powerpc.
>
> Which 405x stuff? Walnut is moved over already. Other boards will
> need to be ported by people that have those boards.
I have no objection with adding #define's to arch/powerpc somewhere
though I'd like to avoid having 36 different .h files per processor
type.
Ben.
next prev parent reply other threads:[~2008-01-22 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 22:43 [PATCH] Various new ibm405 DCRN #defines Joshua Williams
2008-01-21 22:57 ` Benjamin Herrenschmidt
2008-01-22 17:08 ` Joshua Williams
2008-01-22 17:10 ` Josh Boyer
2008-01-22 19:15 ` Joshua Williams
2008-01-22 19:23 ` Josh Boyer
2008-01-22 20:58 ` Benjamin Herrenschmidt [this message]
2008-01-22 19:25 ` Grant Likely
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=1201035528.6807.34.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=joshua.williams@qlogic.com \
--cc=jwboyer@linux.vnet.ibm.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).