From: "Timur Tabi" <timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>,
devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH V2] DTC: Remove support for the legacy DTS source file format.
Date: Fri, 15 Aug 2008 10:17:31 -0500 [thread overview]
Message-ID: <ed82fe3e0808150817k66d6c70fp17774fbd726ea2b2@mail.gmail.com> (raw)
In-Reply-To: <20080815002936.GA9877-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
On Thu, Aug 14, 2008 at 7:29 PM, David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> 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.
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.
How about just printing a warning and saying that the device tree
should be updated with the conversion tool?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-08-15 15:17 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
[not found] ` <20080815002936.GA9877-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-08-15 15:17 ` Timur Tabi [this message]
2008-08-15 15:44 ` Jon Loeliger
[not found] ` <E1KU1Td-0006ub-8O-CYoMK+44s/E@public.gmane.org>
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=ed82fe3e0808150817k66d6c70fp17774fbd726ea2b2@mail.gmail.com \
--to=timur-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=jdl-CYoMK+44s/E@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.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