linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: Please pull from for-2.6.24
Date: Fri, 14 Sep 2007 13:37:10 -0500	[thread overview]
Message-ID: <20070914133710.541f0dbb@weaponx.rchland.ibm.com> (raw)
In-Reply-To: <16B381A2-66F5-4E7A-BDDC-6E536296C933@kernel.crashing.org>

On Fri, 14 Sep 2007 13:24:17 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:

> >>> 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?
> 
> I think that was to the .dts clean ups.  The patch from Roy wasn't  
> part of that.
> 
> http://ozlabs.org/pipermail/linuxppc-dev/2007-September/042499.html

Nope, on the original patch:

http://ozlabs.org/pipermail/linuxppc-dev/2007-July/039289.html

Guess Segher changed his mind :)

> But, I think segher is right in saying we should have tsi109 props if  
> the HW is actually tsi108.

Yeah, that's probably true.

josh

  reply	other threads:[~2007-09-14 18:37 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 [this message]
2007-09-14 18:49         ` Segher Boessenkool
2007-11-16  5:54     ` Zang Roy-r61911

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=20070914133710.541f0dbb@weaponx.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=galak@kernel.crashing.org \
    --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).