devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
	Alessandro Rubini <rubini@gnudd.com>,
	Linus Walleij <linus.walleij@stericsson.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Deepak Saxena <dsaxena@linaro.org>,
	devicetree-discuss@lists.ozlabs.org,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: linux-next: manual merge of the arm-soc tree with the i2c-embedded tree
Date: Tue, 17 Jul 2012 14:10:37 +0100	[thread overview]
Message-ID: <20120717131037.GC27595@sirena.org.uk> (raw)
In-Reply-To: <20120716123550.GE17435@pengutronix.de>

On Mon, Jul 16, 2012 at 02:35:50PM +0200, Wolfram Sang wrote:

> I do know both sides. I easily agree that we have to find a balance
> somewhere to meet both interests. Though, currently my impressions from
> maintaining I2C are:

> a) it is not balanced, but too far on the "let's deploy stuff" side
> b) developers have a tendency to simply map platform_data to bindings
>    and are surprised when told this is often not possible

> which adds burden to the maintainers (who sometimes might not even be
> familiar with devicetree because they are not focused on embedded). And
> I worry about bindings of unmaintained subsystems.

A issue I'm seeing with some of the subsystems mantained by people who
don't work on ARM is that they've got the DT message so strongly that
they're pushing back on people trying to add platform data at all even
on off SoC things that need to work with non-ARM processors.

      parent reply	other threads:[~2012-07-17 13:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120710164130.f38e4d1673f925ddb13914c9@canb.auug.org.au>
     [not found] ` <20120712131231.GH2194@pengutronix.de>
     [not found]   ` <20120712131231.GH2194-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-07-14 21:34     ` linux-next: manual merge of the arm-soc tree with the i2c-embedded tree 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
     [not found]                       ` <50057C1A.80606-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
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
     [not found]             ` <20120716123550.GE17435-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-07-16 19:45               ` Linus Walleij
     [not found]                 ` <CACRpkdaMB-n7XYcxE8QtAm-WrGc2DR0krfTjQZCbvOL1HYep1Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-16 20:04                   ` Chris Ball
2012-07-17 13:10             ` Mark Brown [this message]

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=20120717131037.GC27595@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --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;
as well as URLs for NNTP newsgroup(s).