linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Robert Schwebel" <r.schwebel@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org, Sascha Hauer <sha@pengutronix.de>,
	m8@semihalf.com, Wolfram Sang <wsa@pengutronix.de>
Subject: Re: [PATCH] [POWERPC] mpc5200: Switch mpc5200 dts files to dts-v1 format
Date: Sat, 19 Apr 2008 09:55:58 -0600	[thread overview]
Message-ID: <fa686aa40804190855pa178b42h6f9493b064f728ba@mail.gmail.com> (raw)
In-Reply-To: <20080419133658.GJ13814@pengutronix.de>

On Sat, Apr 19, 2008 at 7:36 AM, Robert Schwebel
<r.schwebel@pengutronix.de> wrote:
> On Fri, Apr 18, 2008 at 09:10:04AM -0700, Grant Likely wrote:
>  > Update dts files to current format
>
>  Is it somehow possible that this device tree stuff is *not* changed over
>  and over again and break everything out there? When people have not even
>  agreed on basic things like decimal vs. hex numbers, the whole idea
>  should be developed out-of-tree, then stabilize and *then* be submitted
>  to the Linux mainline.
>
>  Is it also really necessary to change like "gpt" vs. "timer" and "pic"
>  vs. "interrupt-controller" all the time? If you compare the last
>  mainline kernels, each one got a fundamental change in the naming, each
>  time breaking anyone who doesn't have his stuff in the mainline yet.
>
>  Sorry, but this is simply annoying, and the whole "the only thing we
>  have to do is to define it once and be done then" is crap.

Changing to dts-v1 does *not* break old stuff.  It is just a source
format change.

Neither does the RFC patch for removing the fsl,mpc5200b- compatible strings.

I have no intention of breaking older device trees.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-04-19 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 16:10 [PATCH] [POWERPC] mpc5200: Switch mpc5200 dts files to dts-v1 format Grant Likely
2008-04-19 13:36 ` Robert Schwebel
2008-04-19 15:55   ` Grant Likely [this message]
2008-04-19 18:49   ` Matt Sealey
2008-04-21  8:43 ` Sascha Hauer
2008-04-21 13:21   ` 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=fa686aa40804190855pa178b42h6f9493b064f728ba@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=m8@semihalf.com \
    --cc=r.schwebel@pengutronix.de \
    --cc=sha@pengutronix.de \
    --cc=wsa@pengutronix.de \
    /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).