From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/5] Basic ARM devicetree support
Date: Sat, 14 May 2011 06:14:24 +0200 [thread overview]
Message-ID: <BANLkTi=V337ojovBwiTA9Lnt0OMj0SGTRQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1105120940490.28229@xanadu.home>
On Thu, May 12, 2011 at 9:47 AM, Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> On Wed, 11 May 2011, Russell King - ARM Linux wrote:
>
>> On Wed, May 11, 2011 at 10:44:49PM +0200, Grant Likely wrote:
>> > Right now it merges cleanly with linux-next and the resulting tree
>> > builds and boots at least on qemu. ?Unless you really object, I'm
>> > going to ask Stephen to add the following branch to the /end/ of the
>> > list of trees for linux-next so it can easily be dropped it if it
>> > causes any problems.
>>
>> As far as the set of five patches looks fine to me, I don't have any
>> objections against them. ?So I think we can merge them for .40.
Yay! Thanks Russell!
>> What I've always worried about is the platform stuff, and that's
>> something I'm going to continue worrying about because I don't think
>> we have sufficient review capacity to ensure that we don't end up
>> with lots of stupidities.
Understood, and I agree to a point, but I'm cautiously optimistic that
the review process we talked about heavily this week will be able to
push back on bad bindings to prevent a lot of these problems. It also
helps that we we can cut over to device tree in board ports in stages
without needing a change-everything-flag-day. Devices can be
converted one by one, which will limit the volume of stuff that needs
to be reviewed at one time.
> DT is certainly not a silver bullet. ?Good judgement will be needed as
> to what is put in DT and how it is represented. ?I don't think that it
> would make things worse than they are now though.
+1
> I also do have some concerns about some aspects of DT which I've
> expressed several times in the past. ?However I don't think holding back
> those patches any longer is a solution though.
>
> So consider this as a ACK from my part to merge those patches now. ?This
> will get the ball rolling.
Thanks Nicolas.
g.
next prev parent reply other threads:[~2011-05-14 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 20:44 [PATCH v6 0/5] Basic ARM devicetree support Grant Likely
2011-05-11 21:14 ` Russell King - ARM Linux
2011-05-12 7:47 ` Nicolas Pitre
2011-05-14 4:14 ` Grant Likely [this message]
2011-05-12 0:51 ` 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='BANLkTi=V337ojovBwiTA9Lnt0OMj0SGTRQ@mail.gmail.com' \
--to=grant.likely@secretlab.ca \
--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 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).