From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [patch 5/6] Walnut board support
Date: Tue, 4 Sep 2007 07:37:41 -0500 [thread overview]
Message-ID: <20070904073741.1adab0ba@weaponx.rchland.ibm.com> (raw)
In-Reply-To: <1188741546.3772.5.camel@localhost.localdomain>
On Sun, 02 Sep 2007 08:59:06 -0500
Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> On Mon, 2007-09-03 at 11:11 +1000, David Gibson wrote:
> > On Fri, Aug 31, 2007 at 03:04:54PM -0500, Josh Boyer wrote:
> > > Board support for the PPC405 Walnut evaluation board
> > >
> > > Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
> >
> > [snip]
> > > --- linux-2.6.orig/arch/powerpc/platforms/40x/Kconfig
> > > +++ linux-2.6/arch/powerpc/platforms/40x/Kconfig
> > > @@ -53,13 +53,13 @@
> > > # help
> > > # This option enables support for the IBM PPC405GPr evaluation board.
> > >
> > > -#config WALNUT
> > > -# bool "Walnut"
> > > -# depends on 40x
> > > -# default y
> > > -# select 405GP
> > > -# help
> > > -# This option enables support for the IBM PPC405GP evaluation board.
> > > +config WALNUT
> > > + bool "Walnut"
> > > + depends on 40x
> > > + default y
> > > + select 405GP
> > > + help
> > > + This option enables support for the IBM PPC405GP evaluation board.
> >
> > Surely this needs WANT_DEVICE_TREE, too.
>
> Yes, will be fixed.
Er, actually no it won't. It doesn't need to be selected here, as 40x
in arch/powerpc/platforms/Kconfig.cputype already selects
WANT_DEVICE_TREE. Same thing that ebony and bamboo do for 44x.
josh
next prev parent reply other threads:[~2007-09-04 12:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 20:04 [patch 0/6] Current 4xx patch queue Josh Boyer
2007-08-31 20:04 ` [patch 1/6] Fix bus probe on Bamboo board Josh Boyer
2007-09-03 0:58 ` David Gibson
2007-08-31 20:04 ` [patch 2/6] cuimage for " Josh Boyer
2007-09-03 1:01 ` David Gibson
2007-09-03 13:42 ` Josh Boyer
2007-09-05 1:10 ` David Gibson
2007-09-05 0:40 ` Josh Boyer
2007-09-05 5:46 ` David Gibson
2007-09-05 5:53 ` Josh Boyer
2007-09-05 16:42 ` Josh Boyer
2007-09-07 3:26 ` David Gibson
2007-09-07 1:06 ` David Gibson
2007-08-31 20:04 ` [patch 3/6] Walnut DTS Josh Boyer
2007-09-03 1:08 ` David Gibson
2007-09-02 13:59 ` Josh Boyer
2007-09-04 12:42 ` Josh Boyer
2007-09-05 2:36 ` David Gibson
2007-09-05 0:39 ` Josh Boyer
2007-09-05 11:38 ` Segher Boessenkool
2007-09-05 16:33 ` Josh Boyer
2007-09-07 1:07 ` David Gibson
2007-08-31 20:04 ` [patch 4/6] Walnut defconfig Josh Boyer
2007-08-31 20:04 ` [patch 5/6] Walnut board support Josh Boyer
2007-09-03 1:11 ` David Gibson
2007-09-02 13:59 ` Josh Boyer
2007-09-04 12:37 ` Josh Boyer [this message]
2007-09-05 1:09 ` David Gibson
2007-09-05 3:01 ` David Gibson
2007-08-31 20:04 ` [patch 6/6] Walnut zImage wrapper Josh Boyer
2007-09-03 1:13 ` David Gibson
2007-09-02 13:58 ` Josh Boyer
2007-09-05 16:36 ` Josh Boyer
2007-09-07 1:22 ` David Gibson
2007-09-24 7:49 ` Wolfgang Grandegger
2007-09-24 12:03 ` Josh Boyer
2007-09-24 12:20 ` Wolfgang Grandegger
2007-09-24 12:25 ` Josh Boyer
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=20070904073741.1adab0ba@weaponx.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=dwg@au1.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).