From: neko@bakuhatsu.net (Matt Sealey)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: dts: imx6qdl: make pinctrl nodes board specific
Date: Mon, 4 Nov 2013 16:50:01 -0600 [thread overview]
Message-ID: <CAHCPf3vhyjTnqHXYRj49AL80Z_jGd4LbaRfySjK-=Axkk4FNqA@mail.gmail.com> (raw)
In-Reply-To: <20131101083332.GB10324@S2101-09.ap.freescale.net>
On Fri, Nov 1, 2013 at 3:33 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> On Thu, Oct 31, 2013 at 10:45:08AM -0500, Matt Sealey wrote:
>> I suggested this to Shawn a couple weeks ago and got a bit of pushback.
>>
>> There's probably a ton more to do in this regard to keep the DT
>> per-board more concise, but this drops tree size by a respectable
>> amount on i.MX51 too (just on a tree I have internally, it's something
>> like 8.5KiB) and I can't see any redundant data in the ones he
>> patched.
>>
>> I can follow this up with i.MX51/i.MX53 if nobody is already doing that..
>
> I'm taking care of them as a move of while IMX family.
I'd quite like to push the Efika MX trees at the state they're at,
sometime in the near future; if this work is going to take a while
could I just do it and submit it and see your objections?
I have no merge deadline like Russell, but I would like to put some
closure on some parts of my local tree and sync upstream. My Trello
cards are getting unmanageable ;)
Thanks,
Matt Sealey <neko@bakuhatsu.net>
next prev parent reply other threads:[~2013-11-04 22:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 3:42 [PATCH RFC] ARM: dts: imx6qdl: make pinctrl nodes board specific Shawn Guo
2013-10-28 13:30 ` Dirk Behme
2013-10-29 2:31 ` Shawn Guo
2013-10-31 8:03 ` Sascha Hauer
2013-10-31 10:29 ` Russell King - ARM Linux
2013-10-31 15:45 ` Matt Sealey
2013-10-31 16:09 ` Russell King - ARM Linux
2013-10-31 20:11 ` Matt Sealey
2013-11-01 8:33 ` Shawn Guo
2013-11-04 22:50 ` Matt Sealey [this message]
2013-11-05 2:06 ` Shawn Guo
2013-11-05 22:00 ` Matt Sealey
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='CAHCPf3vhyjTnqHXYRj49AL80Z_jGd4LbaRfySjK-=Axkk4FNqA@mail.gmail.com' \
--to=neko@bakuhatsu.net \
--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).