From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] DT updates for Hummingboard and new Cubox-i
Date: Mon, 20 Jan 2014 09:55:32 +0000 [thread overview]
Message-ID: <20140120095532.GW15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMiych-jeo_eKGgL1qxsYQ=rkb4UQwgGBsG-7+GMbLJWhg@mail.gmail.com>
On Sun, Jan 19, 2014 at 07:34:22PM -0800, Olof Johansson wrote:
> I'm guessing this is going to mess up Shawn's cleanup patches, but
> time has ran out for 3.14 for those so they will need to be respun
> anyway, most likely.
>
> We can apply them to arm-soc's dt branch. I think it's better if we
> merge them since dts files tend to be one of the conflict-ridden areas
> (even if this particular instance isn't). Send the series our way if
> you want, or send a branch pull request, your choice.
There's no conflict, and they build fine according to my autobuilder
which includes arm-soc for-next.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-20 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 18:22 [PATCH 0/2] DT updates for Hummingboard and new Cubox-i Russell King - ARM Linux
2014-01-16 18:22 ` [PATCH 1/2] ARM: move flexcan1 configuration to hummingboard Russell King
2014-01-19 3:26 ` Shawn Guo
2014-01-16 18:22 ` [PATCH 2/2] ARM: add DT support for cubox-i platforms Russell King
2014-01-19 3:18 ` [PATCH 0/2] DT updates for Hummingboard and new Cubox-i Shawn Guo
2014-01-19 18:52 ` Olof Johansson
2014-01-20 0:44 ` Russell King - ARM Linux
2014-01-20 3:34 ` Olof Johansson
2014-01-20 9:55 ` Russell King - ARM Linux [this message]
2014-01-20 20:47 ` Olof Johansson
2014-01-20 21:06 ` Russell King - ARM Linux
2014-01-24 15:09 ` Shawn Guo
2014-01-25 3:44 ` Olof Johansson
2014-01-27 8:16 ` Lucas Stach
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=20140120095532.GW15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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