linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] DT binding management and long-term stability
Date: Thu, 8 Aug 2013 17:34:54 +0100	[thread overview]
Message-ID: <20130808163454.GC27325@e106331-lin.cambridge.arm.com> (raw)

[resending with lakml included]

With the current move to devicetree, several binding additions or
changes appear every day, hampering the use of a current dtb with a
future kernel, or a current kernel with a future dtb, even for a fixed
platform. To solve this and ensure long-term stability, we must have a
stable set of bindings that may be relied upon to function from release
to release. This is critical for the long term health of the ARM Linux
port.

Several steps on path to achieving this have been discussed so far in
person or on list, and there needs to be some consensus reached by the
community as to the steps that still need to be taken (e.g. deprecation
of bindings). There's obvious overlap with several other areas of
interest (e.g. describing non-probable system topologies, ARM SoC
organisation), and it would be extremely useful to have devicetree
maintainers present as part of these discussions.

Thanks,
Mark.

                 reply	other threads:[~2013-08-08 16:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130808163454.GC27325@e106331-lin.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).