From: Zang Roy-r61911 <tie-fei.zang@freescale.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: Please pull from for-2.6.24
Date: 16 Nov 2007 13:54:04 +0800 [thread overview]
Message-ID: <1195192440.7437.1060.camel@localhost.localdomain> (raw)
In-Reply-To: <20070914122510.6dffb747@weaponx.rchland.ibm.com>
On Sat, 2007-09-15 at 01:25, Josh Boyer wrote:
> On Fri, 14 Sep 2007 09:02:04 -0500
> Kumar Gala <galak@kernel.crashing.org> wrote:
>
> >
> > On Sep 13, 2007, at 3:55 PM, Kumar Gala wrote:
> >
> > > Please pull from 'for-2.6.24' branch of
> > >
> > > master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git
> > > for-2.6.24
> > >
> > > to receive the following updates:
> >
> > I've updated the branch with the following changes:
> >
> > > Anton Vorontsov (3):
> > > [POWERPC] MPC832x_RDB: Update dts to use SPI1 in QE,
> register
> > > mmc_spi stub
> >
> > Updated commit message. (let me know if you want me to drop this
> for
> > now and wait til mmc_spi gets merged)
> >
> > > Roy Zang (1):
> > > [POWERPC] Update mpc7448hpc2 device tree to be compatible
> for
> > > tsi109 chip
> >
> > Dropped for now. I doubt we want this based on Segher's comments.
> > (pretty sure its a ts108 on the hpc2 board).
>
> It is a tsi108 on hpc2. Holly has tsi109. From a Linux perspective,
> there is no difference. And the comment Segher made on the list was
> "Looks good, thanks!" So what other comment are you talking about?
Hi, guys
In fact, I was confused by this chain.
Original hpc2 owns tsi108, but the new manufactured board has tsi109.
Roy
prev parent reply other threads:[~2007-11-16 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 20:55 Please pull from for-2.6.24 Kumar Gala
2007-09-14 14:02 ` Kumar Gala
2007-09-14 17:25 ` Josh Boyer
2007-09-14 18:24 ` Kumar Gala
2007-09-14 18:37 ` Josh Boyer
2007-09-14 18:49 ` Segher Boessenkool
2007-11-16 5:54 ` Zang Roy-r61911 [this message]
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=1195192440.7437.1060.camel@localhost.localdomain \
--to=tie-fei.zang@freescale.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).