From: Mark Zhan <rongkai.zhan@windriver.com>
To: Vitaly Bordug <vitb@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 0/3] 82xx: Add the support for Wind River SBC PowerQUICCII
Date: Tue, 17 Jul 2007 13:25:03 +0800 [thread overview]
Message-ID: <1184649903.10499.49.camel@mark> (raw)
In-Reply-To: <20070717044414.03983375@localhost.localdomain>
Hi Vitaly,
When you will send out your 8xx/82xx series patches?
Thanks
Mark Zhan
On Tue, 2007-07-17 at 04:44 +0400, Vitaly Bordug wrote:
> On Mon, 16 Jul 2007 17:01:28 +0800
> Mark Zhan wrote:
>
> > These 3 patches add the powerpc support of Wind River SBC
> > PowerQUICCII.
> >
> I am sorry, but this would intercept with big 8xx/82xx series from
> Scott Wood I am reviewing now. it makes the initial merged code
> more maintainable and powerpc-friendly, but would have some rework
> required in upcoming patches for new BSPs.
>
> OTOH, it would make all the changes below very short and apparent.
> Of course, if something would block those series this one can be considered to merge.
>
>
> > 1) Currently, some mpc82xx platform hooks in mpc82xx_ads.c are
> > actually not specific to ads board. So the 1st patch makes them be
> > shared by different 82xx boards.
> >
> > 2) The 2nd patch make 'cpm_uart_of_init' be able to parse SMC uart in
> > DTS
> >
> > 3) The 3rd patch is the platform codes, defconfig and dts for Wind
> > River SBC PowerQUICCII 82xx board.
> >
> > Any comment is welcome.
> >
> > Thanks
> > Mark Zhan
> >
> > _______________________________________________
> > Linuxppc-dev mailing list
> > Linuxppc-dev@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
>
next prev parent reply other threads:[~2007-07-17 5:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 9:01 [PATCH 0/3] 82xx: Add the support for Wind River SBC PowerQUICCII Mark Zhan
2007-07-17 0:44 ` Vitaly Bordug
2007-07-17 5:25 ` Mark Zhan [this message]
2007-07-17 6:41 ` Vitaly Bordug
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=1184649903.10499.49.camel@mark \
--to=rongkai.zhan@windriver.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=vitb@kernel.crashing.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).