linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: devicetree: Add .dtb files to arch/arm/boot/.gitignore
Date: Tue, 31 Jan 2012 11:52:56 +0000	[thread overview]
Message-ID: <20120131115256.GG2085@linaro.org> (raw)
In-Reply-To: <20120131114659.GE2085@linaro.org>

On Tue, Jan 31, 2012 at 11:46:59AM +0000, Dave Martin wrote:
> On Tue, Jan 31, 2012 at 11:20:24AM +0800, Shawn Guo wrote:
> > On Mon, Jan 30, 2012 at 05:46:14PM +0000, Dave Martin wrote:
> > > Compiled device tree blobs shouldn't be committed in the kernel
> > > tree, so ideally git should ignore them.
> > > 
> > > This patch will enable ignoring of any .dtb files which appear in
> > > arch/arm/boot/
> > > 
> > > Signed-off-by: Dave Martin <dave.martin@linaro.org>
> > 
> > Acked-by: Shawn Guo <shawn.guo@linaro.org>
> > 
> > I added my ack tag on the same patch below, but it died in the end?
> > 
> > http://comments.gmane.org/gmane.linux.ports.arm.kernel/144097
> 
> I don't mind too much which patch goes in -- do we care about whether
> other .dtb files can be included in the kernel?
> 
> 
> I would suggest that it is just plain wrong for _binary_ devicetree
> blobs to appear in the kernel tree, since there is a readily usable
> source form for the same thing (this isn't firmware)
> 
> Do we think that the '.dtb' filename extension might get used foro
> something else?

Never mind, it looks like Grant merged my patch anyway.

Cheers
---Dave

      reply	other threads:[~2012-01-31 11:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 17:46 [PATCH] ARM: devicetree: Add .dtb files to arch/arm/boot/.gitignore Dave Martin
2012-01-31  3:20 ` Shawn Guo
2012-01-31 11:46   ` Dave Martin
2012-01-31 11:52     ` Dave Martin [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=20120131115256.GG2085@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).