From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: mxs: Split M28EVK into SoM and EVK parts
Date: Sat, 28 Jun 2014 23:17:04 +0800 [thread overview]
Message-ID: <20140628151703.GF7869@dragon> (raw)
In-Reply-To: <1403722113-5721-2-git-send-email-marex@denx.de>
On Wed, Jun 25, 2014 at 08:48:33PM +0200, Marek Vasut wrote:
> This patch splits the M28EVK device tree file into a common SoM
> part and an EVK part. This is needed to make it easier for users
> of the SoM to put it into different, non-reference baseboard.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
Applied, thanks.
next prev parent reply other threads:[~2014-06-28 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 18:48 [PATCH 1/2] ARM: dts: mx5: Split M53EVK into SoM and EVK parts Marek Vasut
2014-06-25 18:48 ` [PATCH 2/2] ARM: dts: mxs: Split M28EVK " Marek Vasut
2014-06-28 15:17 ` Shawn Guo [this message]
2014-06-28 15:15 ` [PATCH 1/2] ARM: dts: mx5: Split M53EVK " Shawn Guo
2014-07-09 11:55 ` Marek Vasut
2014-07-14 14:49 ` Shawn Guo
2014-07-14 18:57 ` Marek Vasut
2014-07-09 11:56 ` [PATCH] ARM: dts: mx5: Move the USB pinmux to USB node on M53EVK Marek Vasut
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=20140628151703.GF7869@dragon \
--to=shawn.guo@linaro.org \
--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).