From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH] spi: tegra114: add spi driver
Date: Wed, 20 Feb 2013 11:00:02 -0700 [thread overview]
Message-ID: <51250F22.8050401@wwwdotorg.org> (raw)
In-Reply-To: <20130220175721.GW2726@opensource.wolfsonmicro.com>
On 02/20/2013 10:57 AM, Mark Brown wrote:
> On Wed, Feb 20, 2013 at 10:36:41AM -0700, Stephen Warren wrote:
>> On 02/20/2013 10:31 AM, Mark Brown wrote:
>
>>> Since we can extend the list of clocks it doesn't seem like
>>> there's much issue here, especially if some of them are
>>> optional?
>
>> Yes, there's certainly a way to extend the binding in a
>> backwards-compatible way.
>
>> However, I have seen in Rob and/or Grant push back on not fully
>> defining bindings in the past - i.e. actively planning to
>> initially create a minimal binding and extend it in the future,
>> rather than completely defining it up-front.
>
> That sounds like the current stuff with a minimal definition is
> OK?
I'm personally OK with defining a minimal binding first and extending
it later. But, I'm worried if when we actually try to extend the
binding later, we'll get push-back.
next prev parent reply other threads:[~2013-02-20 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 13:38 Laxman Dewangan
2013-02-19 18:16 ` Stephen Warren
2013-02-20 12:29 ` Laxman Dewangan
2013-02-20 13:11 ` Mark Brown
2013-02-20 13:26 ` Laxman Dewangan
2013-02-20 13:34 ` Mark Brown
2013-02-20 17:25 ` Stephen Warren
2013-02-20 17:31 ` Mark Brown
2013-02-20 17:36 ` Stephen Warren
2013-02-20 17:57 ` Mark Brown
2013-02-20 18:00 ` Stephen Warren [this message]
2013-02-21 5:48 ` Laxman Dewangan
2013-02-21 9:56 ` Peter De Schrijver
2013-02-21 17:29 ` Mark Brown
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=51250F22.8050401@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=swarren@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome