From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2013-discuss] [RFC] of: Allow for experimental device tree bindings
Date: Wed, 23 Oct 2013 20:56:04 +0200 [thread overview]
Message-ID: <20131023185603.GB7863@ulmo.nvidia.com> (raw)
In-Reply-To: <1382547916.8522.42.camel@shinybook.infradead.org>
On Wed, Oct 23, 2013 at 06:05:16PM +0100, David Woodhouse wrote:
> On Wed, 2013-10-23 at 09:55 -0700, Guenter Roeck wrote:
> >
> > So to avoid tainting the kernel and clogging the kernel log I'll have
> > to remove all the "!" from the dt sources, or not use any "!" in the
> > dt bindings in the first place. Given that, not sure if anyone will
> > really use this mechanism. And CONFIG_OF_EXPERIMENTAL/CONFIG_UNSTABLE_DT
> > might have the same ultimate fate as CONFIG_EXPERIMENTAL.
>
> It's not as if it's hard for you to patch out the check if you really
> want to do that. This is about making it clear to people what they
> should expect if they use staging code/bindings.
I agree. The kernel is open source, so people are free to patch it in
any way they want. The best we can do is to come up with a good solution
in an upstream kernel. But there's no way we can control things beyond
that, and we don't have to.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131023/d46e88e1/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ksummit-2013-discuss-cunTk1MwBs98uUxBSJOaYoYkZiVZrdSR2LY78lusg7I@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [Ksummit-2013-discuss] [RFC] of: Allow for experimental device tree bindings
Date: Wed, 23 Oct 2013 20:56:04 +0200 [thread overview]
Message-ID: <20131023185603.GB7863@ulmo.nvidia.com> (raw)
In-Reply-To: <1382547916.8522.42.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Wed, Oct 23, 2013 at 06:05:16PM +0100, David Woodhouse wrote:
> On Wed, 2013-10-23 at 09:55 -0700, Guenter Roeck wrote:
> >
> > So to avoid tainting the kernel and clogging the kernel log I'll have
> > to remove all the "!" from the dt sources, or not use any "!" in the
> > dt bindings in the first place. Given that, not sure if anyone will
> > really use this mechanism. And CONFIG_OF_EXPERIMENTAL/CONFIG_UNSTABLE_DT
> > might have the same ultimate fate as CONFIG_EXPERIMENTAL.
>
> It's not as if it's hard for you to patch out the check if you really
> want to do that. This is about making it clear to people what they
> should expect if they use staging code/bindings.
I agree. The kernel is open source, so people are free to patch it in
any way they want. The best we can do is to come up with a good solution
in an upstream kernel. But there's no way we can control things beyond
that, and we don't have to.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-23 18:56 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 15:06 [RFC] of: Allow for experimental device tree bindings Thierry Reding
2013-10-23 15:06 ` Thierry Reding
2013-10-23 16:05 ` [Ksummit-2013-discuss] " David Woodhouse
2013-10-23 16:05 ` David Woodhouse
2013-10-23 16:55 ` Guenter Roeck
2013-10-23 16:55 ` Guenter Roeck
2013-10-23 17:05 ` David Woodhouse
2013-10-23 17:05 ` David Woodhouse
2013-10-23 18:56 ` Thierry Reding [this message]
2013-10-23 18:56 ` Thierry Reding
2013-10-23 18:51 ` Thierry Reding
2013-10-23 18:51 ` Thierry Reding
2013-10-24 22:26 ` Stephen Warren
2013-10-24 22:26 ` Stephen Warren
2013-10-25 8:22 ` Thierry Reding
2013-10-25 8:22 ` Thierry Reding
2013-10-25 8:45 ` Stephen Warren
2013-10-25 8:45 ` Stephen Warren
2013-10-23 16:33 ` Stephen Warren
2013-10-23 16:33 ` Stephen Warren
2013-10-23 17:20 ` [Ksummit-2013-discuss] " Wolfram Sang
2013-10-23 17:20 ` Wolfram Sang
2013-10-23 18:59 ` Thierry Reding
2013-10-23 18:59 ` Thierry Reding
2013-10-23 19:34 ` Jason Gunthorpe
2013-10-23 19:34 ` Jason Gunthorpe
2013-10-23 19:58 ` Thierry Reding
2013-10-23 19:58 ` Thierry Reding
2013-10-23 21:08 ` Jason Gunthorpe
2013-10-23 21:08 ` Jason Gunthorpe
2013-10-24 8:04 ` Thierry Reding
2013-10-24 8:04 ` Thierry Reding
2013-10-24 17:32 ` Jason Gunthorpe
2013-10-24 17:32 ` Jason Gunthorpe
2013-10-23 21:13 ` Andy Lutomirski
2013-10-23 21:13 ` Andy Lutomirski
2013-10-23 19:40 ` Wolfram Sang
2013-10-23 19:40 ` Wolfram Sang
2013-10-23 20:05 ` Thierry Reding
2013-10-23 20:05 ` Thierry Reding
2013-10-24 8:34 ` Grant Likely
2013-10-24 8:34 ` Grant Likely
2013-10-24 8:50 ` Thierry Reding
2013-10-24 8:50 ` Thierry Reding
2013-10-24 20:26 ` Matt Sealey
2013-10-24 20:26 ` Matt Sealey
2013-10-24 22:29 ` Stephen Warren
2013-10-24 22:29 ` Stephen Warren
2013-10-24 18:39 ` jonsmirl at gmail.com
2013-10-24 18:39 ` jonsmirl-Re5JQEeQqe8AvxtiuMwx3w
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=20131023185603.GB7863@ulmo.nvidia.com \
--to=thierry.reding@gmail.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 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.