linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: imx: device tree changes for 3.15, take 1
Date: Fri, 07 Feb 2014 11:04:30 +0100	[thread overview]
Message-ID: <4771497.sfdTTRjnSv@phil> (raw)
In-Reply-To: <20140205122258.GA13821@S2101-09.ap.freescale.net>

Hi Shawn,

Am Mittwoch, 5. Februar 2014, 20:23:01 schrieb Shawn Guo:
>  - Make pinctrl nodes board specific to avoid floating board specific
>    device tree blob with so many unused pinctrl data.

can you take a look at "dtc: add ability to make nodes conditional on them 
being referenced" [0] to see if it can help to solve the floating pinctrl 
problem more generic in the future?


Heiko


[0] http://www.spinics.net/lists/arm-kernel/msg303967.html

  parent reply	other threads:[~2014-02-07 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 12:23 [GIT PULL] ARM: imx: device tree changes for 3.15, take 1 Shawn Guo
2014-02-06 13:45 ` Arnd Bergmann
2014-02-06 15:01   ` Shawn Guo
2014-02-09 12:16   ` Shawn Guo
2014-02-10 15:19     ` Arnd Bergmann
2014-02-07 10:04 ` Heiko Stübner [this message]
2014-02-10  6:33   ` Shawn Guo

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=4771497.sfdTTRjnSv@phil \
    --to=heiko@sntech.de \
    --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).