From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DeviceTree fixes for 3.8
Date: Mon, 14 Jan 2013 15:17:23 -0600 [thread overview]
Message-ID: <50F475E3.5060409@gmail.com> (raw)
Linus,
Please pull these 2 small fixes for DT. The move to common dtb build rules
went in through the DT tree, so I'm taking the fixes too.
Rob
The following changes since commit 9931faca02c604c22335f5a935a501bb2ace6e20:
Linux 3.8-rc3 (2013-01-09 18:59:55 -0800)
are available in the git repository at:
git://sources.calxeda.com/kernel/linux.git tags/dt-fixes-for-3.8
for you to fetch changes up to 1ab3681271c84b7f926be9ae3be1d769b7e933e9:
ARM: dts: prevent *.dtb from always being rebuilt (2013-01-14 08:08:31 -0600)
----------------------------------------------------------------
DeviceTree fixes for 3.8
2 fixes to prevent unconditional re-compile of dts files on arm and arm64.
----------------------------------------------------------------
Stephen Warren (2):
arm64: dts: prevent *.dtb from always being rebuilt
ARM: dts: prevent *.dtb from always being rebuilt
arch/arm/boot/dts/Makefile | 1 +
arch/arm64/boot/dts/Makefile | 1 +
2 files changed, 2 insertions(+)
reply other threads:[~2013-01-14 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50F475E3.5060409@gmail.com \
--to=robherring2@gmail.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).