From: heiko@sntech•de (Heiko Stübner)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/2] ARM: dts: mvebu: split SolidRun CuBox into variants
Date: Wed, 28 May 2014 00:24:58 +0200 [thread overview]
Message-ID: <32589428.8iAxtgFCnl@phil> (raw)
In-Reply-To: <538508A5.2010809@gmail.com>
Am Dienstag, 27. Mai 2014, 23:50:29 schrieb Sebastian Hesselbarth:
> On 05/27/2014 11:35 PM, Jason Cooper wrote:
> > On Tue, May 27, 2014 at 07:28:09PM +0200, Sebastian Hesselbarth wrote:
> >> On 05/27/2014 06:11 PM, Jason Cooper wrote:
> >>> On Mon, May 26, 2014 at 11:33:29PM +0200, Sebastian Hesselbarth wrote:
> > info. It may be useful here, but I'd like to hear from the DT
> > maintainers how they want it used. eg: most popular first, like you
> > have it, or oldest first
> >
> > dove-cubox-es.dts
> > +--> dove-cubox.dts
>
> In the cubox case, this is not possible. ES has a misrouted
> card-detection for sdhci, this requires an additional property.
> There is no way to remove a property once it is written down in
> any of the files included. But you know about that already.
dtc knows "/delete-property/" [0], but I may be missing something here.
[0] https://lists.ozlabs.org/pipermail/devicetree-discuss/2012-August/018169.html
next prev parent reply other threads:[~2014-05-27 22:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 21:33 [PATCH 1/2] dt-binding: add vendor prefix for SolidRun Sebastian Hesselbarth
2014-05-26 21:33 ` [PATCH 2/2] ARM: dts: mvebu: split SolidRun CuBox into variants Sebastian Hesselbarth
2014-05-27 16:11 ` Jason Cooper
2014-05-27 16:30 ` Sebastian Hesselbarth
2014-05-27 16:38 ` Jason Cooper
2014-05-27 17:02 ` Olof Johansson
2014-05-27 17:28 ` Sebastian Hesselbarth
2014-05-27 21:35 ` Jason Cooper
2014-05-27 21:50 ` Sebastian Hesselbarth
2014-05-27 22:24 ` Heiko Stübner [this message]
2014-05-27 22:37 ` Sebastian Hesselbarth
2014-05-27 22:00 ` [PATCH v2 " Sebastian Hesselbarth
2014-05-28 22:50 ` [PATCH 1/2] dt-binding: add vendor prefix for SolidRun Rob Herring
2014-06-20 20:58 ` Jason Cooper
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=32589428.8iAxtgFCnl@phil \
--to=heiko@sntech$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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