From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Marian Balakowicz" <m8@semihalf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Update TQM5200, CM5200 and Motion-PRO _defconfig and .dts files
Date: Thu, 17 Jan 2008 09:05:21 -0700 [thread overview]
Message-ID: <fa686aa40801170805g46eb4686y35c65276779d5244@mail.gmail.com> (raw)
In-Reply-To: <20080117143024.15372.95923.stgit@hekate.izotz.org>
On 1/17/08, Marian Balakowicz <m8@semihalf.com> wrote:
> Updates include:
> - set soc node compatible property to "fsl,mpc5200-immr"
On these three boards; which have the original mpc5200 and which have
the mpc5200b?
I'm not going to pick up this patch immediately, I've got an invasive
set of mpc5200 device tree cleanups which need to go in first. After
that I'll revisit your changes here.
> - update i2c device tree nodes
> - add mdio node
> - add lpb bus node and flash device (without partitions defined)
> - add second mscan node for Motio-PRO
> - add rtc i2c nodes and enable RTC in _defconfigs
> - use SLUB insteand of SLAB
> - enable printk timestamp
Can you split the defconfig changes into a separate patch... That
being said, how do you feel about merging all the 5200 defconfigs into
a single defconfig? They are all multiplatform after all and it would
make maintenance easier.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-01-17 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 14:31 [PATCH] [POWERPC] Update TQM5200, CM5200 and Motion-PRO _defconfig and .dts files Marian Balakowicz
2008-01-17 16:05 ` Grant Likely [this message]
2008-01-17 18:02 ` Marian Balakowicz
2008-01-17 18:23 ` Grant Likely
2008-01-17 22:05 ` Marian Balakowicz
2008-01-18 3:41 ` Olof Johansson
2008-01-23 11:31 ` Marian Balakowicz
2008-01-23 12:54 ` Wolfgang Denk
2008-01-23 16:27 ` 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=fa686aa40801170805g46eb4686y35c65276779d5244@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=m8@semihalf.com \
/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).