From: Jamie Iles <jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
To: Artem Bityutskiy <dedekind1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCHv6] mtd: gpio-nand: add device tree bindings
Date: Fri, 14 Oct 2011 15:43:37 +0100 [thread overview]
Message-ID: <20111014144337.GB25079@totoro> (raw)
In-Reply-To: <1318602329.12351.143.camel@sauron>
On Fri, Oct 14, 2011 at 05:25:21PM +0300, Artem Bityutskiy wrote:
> On Fri, 2011-10-14 at 15:21 +0100, Jamie Iles wrote:
> > > the top of my head, it is logical when things go like this: I have a
> > > kernel with working platform data, but I can change that dynamically by
> > > feeding it a device tree configuration. Hmm?
> >
> > I think in general platform data and device tree should be mutually
> > exclusive.
>
> OK, but would you please confirm this by pointing to some docs or
> discussions, or may be people from devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> could confirm that?
I found https://lwn.net/Articles/449058/ from Grant that I think covers
it, but that's the best I could find written down!
Jamie
next prev parent reply other threads:[~2011-10-14 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 23:10 [PATCHv6] mtd: gpio-nand: add device tree bindings Jamie Iles
2011-10-14 13:48 ` Artem Bityutskiy
2011-10-14 14:21 ` Jamie Iles
2011-10-14 14:25 ` Artem Bityutskiy
2011-10-14 14:43 ` Jamie Iles [this message]
2011-10-15 3:04 ` Grant Likely
[not found] ` <20111015030415.GA8274-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-10-15 5:09 ` Jamie Iles
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=20111014144337.GB25079@totoro \
--to=jamie-wmlquqddiekakbo8gow8eq@public.gmane.org \
--cc=dedekind1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox