From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: add device tree blobs to .gitignore
Date: Thu, 15 Dec 2011 14:47:57 +0000 [thread overview]
Message-ID: <20111215144757.GA2081@linaro.org> (raw)
In-Reply-To: <1323808612-14976-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Tue, Dec 13, 2011 at 09:36:52PM +0100, Uwe Kleine-K??nig wrote:
> *.dtb files are a build result and so should be ignored.
>
> Signed-off-by: Uwe Kleine-K??nig <u.kleine-koenig@pengutronix.de>
Should this actually be global?
It looks like at least powerpc, microblaze and openrisc may generate
.dtbs and I don't see any local .gitignore entries for those.
Since the dtc tool itself is global (i.e., in an arch-independent
scripts dir instead of somewhere arch-specific), it could be argued that
other related stuff should be global too.
Cheers
---Dave
next prev parent reply other threads:[~2011-12-15 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 20:36 [PATCH] ARM: add device tree blobs to .gitignore Uwe Kleine-König
2011-12-15 2:25 ` Shawn Guo
2011-12-15 14:47 ` Dave Martin [this message]
2011-12-15 21:30 ` Uwe Kleine-König
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=20111215144757.GA2081@linaro.org \
--to=dave.martin@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).