All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomba@iki.fi>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [pull] tilcdc-next for 3.9
Date: Mon, 18 Feb 2013 14:40:12 +0200	[thread overview]
Message-ID: <5122212C.4070808@iki.fi> (raw)
In-Reply-To: <CAF6AEGuqw=6wt4M2YsePP0dxUaMRMKzZmjYtVAMUD5_1ZDESsg@mail.gmail.com>

On 2013-02-18 14:35, Rob Clark wrote:
> On Mon, Feb 18, 2013 at 7:32 AM, Tomi Valkeinen <tomba@iki.fi> wrote:
>> On 2013-02-18 14:26, Rob Clark wrote:
>>
>>> So I'm not going to get too hung up on supporting current DT bindings
>>> in the future when we have something better.  But I needed something
>>
>> I may be mistaken, but my understanding is that DT bindings are like
>> kernel's userspace APIs. After they have been merged, they have to work
>> in the future kernels also.
> 
> and that probably *eventually* makes sense when dts files are kicked
> out of the kernel.  For now, it doesn't really seem useful, unlike
> maintaining compatibility for userspace ABI's.

Why does that matter? Afaik, the dts files are in the kernel for
convenience, and as examples. You can as well have the DT data in your
bootloader.

Or has there been a clear decision that while the dts files are in the
kernel, they are considered unstable?

 Tomi

  reply	other threads:[~2013-02-18 12:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17 23:02 [pull] tilcdc-next for 3.9 Rob Clark
2013-02-18  9:02 ` Tomi Valkeinen
2013-02-18 10:03   ` Daniel Vetter
2013-02-18 10:16     ` Tomi Valkeinen
2013-02-18 16:49       ` Daniel Vetter
2013-02-18 12:32     ` Rob Clark
2013-02-18 12:26   ` Rob Clark
2013-02-18 12:32     ` Tomi Valkeinen
2013-02-18 12:35       ` Rob Clark
2013-02-18 12:40         ` Tomi Valkeinen [this message]
2013-02-18 14:46           ` Rob Clark

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=5122212C.4070808@iki.fi \
    --to=tomba@iki.fi \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robdclark@gmail.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 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.