From: Daniel Lezcano <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Rob Herring <rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Alexander Kochetkov
<al.kochet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Question regarding back compatibility for DT
Date: Tue, 21 Mar 2017 22:56:46 +0100 [thread overview]
Message-ID: <20170321215646.GC10342@mai> (raw)
In-Reply-To: <CABGGisyuq6=3RTKZ7ceUjt_iFZVag0EMViqmXSKSg5bM2-o-Cw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Mar 21, 2017 at 11:27:37AM -0500, Rob Herring wrote:
> On Tue, Mar 21, 2017 at 10:58 AM, Daniel Lezcano
> <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:
> > Hi Rob, dt people,
> >
> > is it acceptable a driver is changed using a new DT binding but becomes
> > incompatible with the old DT files ?
> >
> > IOW, is it possible to change the DT and the driver without supporting the old
> > DT format, forcing an update of the DT and the kernel ?
>
> If you want a global rule, then no it is not okay. However, it depends
> on the platform and it's users. I just ask that breaking compatibility
> and why is highlighted in the commit message and the platform
> maintainer is okay with it.
Thanks for the clarification. I will ask the maintainer if breaking the
compatibility is ok.
That shows how important is to wisely choose the right binding.
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-03-21 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 15:58 Question regarding back compatibility for DT Daniel Lezcano
2017-03-21 16:16 ` Warner Losh
[not found] ` <CANCZdfpwRSSEhBcr_BrvRj4MfBbMHSYpC+wJvm7fU6h=GXkqtg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-21 16:36 ` Rob Herring
2017-03-21 16:27 ` Rob Herring
[not found] ` <CABGGisyuq6=3RTKZ7ceUjt_iFZVag0EMViqmXSKSg5bM2-o-Cw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-21 21:56 ` Daniel Lezcano [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=20170321215646.GC10342@mai \
--to=daniel.lezcano-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=al.kochet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-QSEj5FYQhm4dnm+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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.