mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linus Walleij <linus.walleij@stericsson.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Alessandro Rubini <rubini@gnudd.com>,
	linux-kernel@vger.kernel.org,
	Grant Likely <grant.likely@secretlab.ca>,
	Deepak Saxena <dsaxena@linaro.org>,
	linux-next@vger.kernel.org, Olof Johansson <olof@lixom.net>,
	Lee Jones <lee.jones@linaro.org>,
	devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: linux-next: manual merge of the arm-soc tree with the i2c-embedded tree
Date: Mon, 16 Jul 2012 16:04:25 -0400	[thread overview]
Message-ID: <874np7jwvq.fsf@octavius.laptop.org> (raw)
In-Reply-To: <CACRpkdaMB-n7XYcxE8QtAm-WrGc2DR0krfTjQZCbvOL1HYep1Q@mail.gmail.com> (Linus Walleij's message of "Mon, 16 Jul 2012 21:45:29 +0200")

Hi,

On Mon, Jul 16 2012, Linus Walleij wrote:
>> Uhm, I seem to have missed that bindings are deemed more "flexible" as
>> long as they are coupled to in-kernel dts files? Is that discussed
>> somewhere? I do wonder about it...
>
> Well patches like this are sent out but not commented on from
> the perspective of binding stability. So of course, they get merged.
>
> Have a look at this commit:
>
> commit 7f217794ffa72f208a250b79ab0b7ea3de19677f
> Author: Arnd Bergmann <arnd@arndb.de>
> Date:   Sun May 13 00:14:24 2012 -0400
>
>     mmc: dt: Consolidate DT bindings
>
> This is deleting custom properties from DTS files without
> adding any code to fallback-support them on old device trees.

I agree with your point, but just as an FYI: this patch did involve
a conversation about binding stability, and left some attributes
(e.g. ti,non-removable) purposefully alone (and different to the
new generic MMC bindings) to preserve backwards compatibility:

http://article.gmane.org/gmane.linux.kernel.samsung-soc/10409

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2012-07-16 20:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10  6:41 Stephen Rothwell
2012-07-10  6:50 ` Stephen Rothwell
2012-07-10  8:38 ` Wolfram Sang
2012-07-12 13:12 ` Wolfram Sang
2012-07-12 15:54   ` Arnd Bergmann
2012-07-13 11:03     ` Lee Jones
2012-07-14 21:34   ` Linus Walleij
2012-07-16 10:17     ` Wolfram Sang
2012-07-16 11:31       ` Lee Jones
2012-07-16 13:00         ` Wolfram Sang
2012-07-16 13:55           ` Lee Jones
2012-07-17 13:06         ` Mark Brown
2012-07-17 13:30           ` Lee Jones
2012-07-17 13:35             ` Mark Brown
2012-07-17 14:02               ` Lee Jones
2012-07-17 14:22                 ` Mark Brown
2012-07-17 14:52                   ` Lee Jones
2012-07-17 15:20                     ` Mark Brown
2012-07-18  5:33                       ` Shawn Guo
2012-07-18  9:59                         ` Mark Brown
2012-07-18 10:29                           ` Lee Jones
2012-07-18 10:33                             ` Mark Brown
2012-07-18 10:43                               ` Lee Jones
2012-07-18  7:35                       ` Lee Jones
2012-07-18 11:12                         ` Mark Brown
2012-07-18 11:24                           ` Lee Jones
2012-07-16 11:37       ` Linus Walleij
2012-07-16 12:35         ` Wolfram Sang
2012-07-16 19:45           ` Linus Walleij
2012-07-16 20:04             ` Chris Ball [this message]
2012-07-17 13:10           ` Mark Brown
2012-07-19  5:28 Stephen Rothwell
2012-09-13  6:41 Stephen Rothwell
2012-09-13  7:09 ` Uwe Kleine-König
2012-11-15  5:27 Stephen Rothwell

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=874np7jwvq.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dsaxena@linaro.org \
    --cc=grant.likely@secretlab.ca \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=rubini@gnudd.com \
    --cc=sfr@canb.auug.org.au \
    --cc=swarren@wwwdotorg.org \
    --cc=w.sang@pengutronix.de \
    /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

Powered by JetHome