From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] venice2: move device tree to fix build error
Date: Thu, 20 Feb 2014 09:17:48 -0700 [thread overview]
Message-ID: <53062AAC.8080904@wwwdotorg.org> (raw)
In-Reply-To: <1392884322-30854-1-git-send-email-yamada.m@jp.panasonic.com>
On 02/20/2014 01:18 AM, Masahiro Yamada wrote:
> Commit 5ab502cb gathered all device tree sources
> to arch/$(ARCH)/dts/.
> So tegra124-venice2.dts also must go to arch/arm/dts directory
> to build venice2 board.
>
> (Commit 5ab502cb had been posted before venice2 board support
> was merged. So an unvisible conflict happened.)
Since all the other DTS have moved likewise,
Acked-by: Stephen Warren <swarren@nvidia.com>
(although not that Tom Warren is the Tegra U-Boot maintainer).
> arch/arm/dts/Makefile | 5 +--
> arch/arm/dts/tegra124-venice2.dts | 84 +++++++++++++++++++++++++++++++++++
> board/nvidia/dts/tegra124-venice2.dts | 84 -----------------------------------
I'm assuming the file was moved with zero changes. "git format-patch -M"
would have been useful to make this clear.
next prev parent reply other threads:[~2014-02-20 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 8:18 [U-Boot] [PATCH] venice2: move device tree to fix build error Masahiro Yamada
2014-02-20 16:17 ` Stephen Warren [this message]
2014-02-20 17:08 ` Tom Warren
2014-02-20 17:16 ` Tom Rini
2014-02-20 17:17 ` Tom Rini
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=53062AAC.8080904@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.