linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: vf610-colibri: split device tree for carrier boards
Date: Tue, 22 Jul 2014 10:14:04 +0800	[thread overview]
Message-ID: <20140722021403.GP8537@dragon> (raw)
In-Reply-To: <1405693518-28293-1-git-send-email-stefan@agner.ch>

On Fri, Jul 18, 2014 at 04:25:18PM +0200, Stefan Agner wrote:
> The Colibri VF61 is a module which needs a carrier board to actually
> run. Different carrier board have different hardware support, hence
> we should reflect this in the device tree files. This patch adds the
> Colibri Evaluation Board, which supports almost all peripherals
> defined in the Colibri standard.
> 
> Also align the compatible naming, file splitting and file naming with
> the scheme which was choosen for the Tegra based modules.
> 
> Signed-off-by: Stefan Agner <stefan@agner.ch>

Applied, thanks.

      reply	other threads:[~2014-07-22  2:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 14:25 [PATCH] ARM: dts: vf610-colibri: split device tree for carrier boards Stefan Agner
2014-07-22  2:14 ` Shawn Guo [this message]

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=20140722021403.GP8537@dragon \
    --to=shawn.guo@freescale.com \
    --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).