linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
	Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH V2] DTC: Remove support for the legacy DTS source file format.
Date: Sat, 16 Aug 2008 15:06:30 +1000	[thread overview]
Message-ID: <20080816050630.GA12072@yookeroo.seuss> (raw)
In-Reply-To: <E1KU1Td-0006ub-8O@jdl.com>

On Fri, Aug 15, 2008 at 10:44:33AM -0500, Jon Loeliger wrote:
> > On Thu, Aug 14, 2008 at 7:29 PM, David Gibson
> > <david@gibson.dropbear.id.au> wrote:
> > > On Thu, Aug 14, 2008 at 06:02:43PM -0500, Jon Loeliger wrote:
> > >> Now that all in-kernel-tree DTS files are properly /dts-v1/,
> > >> remove direct support for the older, un-numbered DTS
> > >> source file format.
> > >
> > > Um.. why?  I just don't see a compelling reason to remove this
> > > backwards compatibility.  It costs us very little to keep it around
> > > indefinitely.
> 
> Because we are going to get rid of the cruft, simplify things,
> and move forward.  Really.  This was the plan from the onset.

Uh.. removing compatibility for the old format was never part of *my*
plan for the change.  Discourage any further use of the v0 format,
yes, remove support for, no.

I just don't see a benefit to this.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

      reply	other threads:[~2008-08-16  5:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 23:02 [PATCH V2] DTC: Remove support for the legacy DTS source file format Jon Loeliger
2008-08-15  0:29 ` David Gibson
2008-08-15 15:17   ` Timur Tabi
2008-08-15 15:44     ` Jon Loeliger
2008-08-16  5:06       ` David Gibson [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=20080816050630.GA12072@yookeroo.seuss \
    --to=david@gibson.dropbear.id.au \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.com \
    /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).