From: Jon Loeliger <jdl@jdl.com>
To: "Timur Tabi" <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: [PATCH V2] DTC: Remove support for the legacy DTS source file format.
Date: Fri, 15 Aug 2008 10:44:33 -0500 [thread overview]
Message-ID: <E1KU1Td-0006ub-8O@jdl.com> (raw)
In-Reply-To: <ed82fe3e0808150817k66d6c70fp17774fbd726ea2b2@mail.gmail.com>
> 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.
> I agree, why are we removing backwards compatibility? The dts-v1
> format isn't that old, so I'm sure there are plenty of device trees
> out there, especially on our BSPs, that haven't been updated yet.
They can run the conversion tool and be fine.
> How about just printing a warning and saying that the device tree
> should be updated with the conversion tool?
How about all the in-tree DTS files are already V1?
jdl
next prev parent reply other threads:[~2008-08-15 15:44 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 [this message]
2008-08-16 5:06 ` David Gibson
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=E1KU1Td-0006ub-8O@jdl.com \
--to=jdl@jdl.com \
--cc=devicetree-discuss@ozlabs.org \
--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).