linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Convert remaining dts-v0 files to v1
Date: Thu, 15 May 2008 07:03:35 -0500	[thread overview]
Message-ID: <20080515070335.5d9a98e5@zod.rchland.ibm.com> (raw)
In-Reply-To: <20080515064639.GB30996@yookeroo.seuss>

On Thu, 15 May 2008 16:46:39 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> At the moment we have a mixture of left-over version 0 and new-format
> version 1 files in arch/powerpc/boot/dts.  This is potentially
> confusing to people new to the dts format attempting to figure it out.
> 
> So, this patch converts all the as-yet unconverted dts v0 files and
> converts them to v1.  They're mechanically-converted, and not hand
> tweaked so in some cases they're not 100% in keeping with usual v1
> style, but the convertor program does have some heuristics so the
> discrepancies aren't too bad.
> 
> I have checked that this patch produces no changes to the resulting
> dtb binaries.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

The only dts affected that isn't something I maintain or wrote (holly)
is the ps3.dts.  How do we want to handle this one?  I'd like to get it
into my tree soon (today/tomorrow) as I'm queuing up patches for .27 at
the moment.

As for the 4xx and holly dts changes:

Acked-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>

josh

  reply	other threads:[~2008-05-15 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  6:46 Convert remaining dts-v0 files to v1 David Gibson
2008-05-15 12:03 ` Josh Boyer [this message]
2008-05-15 20:22 ` Geoff Levand
2008-05-15 23:17   ` Josh Boyer
2008-05-16  0:52     ` Paul Mackerras
2008-05-16  1:02       ` 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=20080515070335.5d9a98e5@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --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).