From: Gary Coulbourne <bear@bears.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add support for dtb file in /boot directory on target
Date: Wed, 19 Dec 2012 12:10:50 -0500 [thread overview]
Message-ID: <50D1F51A.3080901@bears.org> (raw)
In-Reply-To: <50D0A947.5090107@mind.be>
On 12/18/2012 12:35 PM, Arnout Vandecappelle wrote:
> Could you also resend this patch with git send-email? (See its man
> page for how to configure it for gmail.)
Sure thing.
> Perhaps the whitespace is correct and gmail ate it, but just to be sure:
> indentation should be one tab.
I assume gmail ate it. I use tabs by default in makefile-ish files.
> Or are there use cases where you want the DTB in /boot, but not the
> kernel image?
It seems the logical place for the dtb to live, with the kernel, bit it
is possible someone would not want that.
Is there a consensus from the folks on the mailing list about what
should be done with the dtb?
Peace,
Gary
prev parent reply other threads:[~2012-12-19 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 21:43 [Buildroot] [PATCH] Add support for dtb file in /boot directory on target Gary Coulbourne
2012-12-18 17:35 ` Arnout Vandecappelle
2012-12-19 17:10 ` Gary Coulbourne [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=50D1F51A.3080901@bears.org \
--to=bear@bears.org \
--cc=buildroot@busybox.net \
/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