From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] boot/at91bootstrap3: implement custom tarball
Date: Mon, 23 Dec 2019 23:45:25 +0100 [thread overview]
Message-ID: <20191223234525.107c5389@windsurf> (raw)
In-Reply-To: <1576508766-25676-2-git-send-email-eugen.hristev@microchip.com>
On Mon, 16 Dec 2019 15:06:34 +0000
<Eugen.Hristev@microchip.com> wrote:
> From: Eugen Hristev <eugen.hristev@microchip.com>
>
> Implement possibility to take AT91Bootstrap as a custom tarball.
>
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
> ---
> Changes in v2:
> - use BR_NO_CHECK_HASH_FOR += $(AT91BOOTSTRAP3_SOURCE)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-23 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 15:06 [Buildroot] [PATCH v2 1/2] configs/atmel: fix at91bootstrap custom tarball call function Eugen.Hristev at microchip.com
2019-12-16 15:06 ` [Buildroot] [PATCH v2 2/2] boot/at91bootstrap3: implement custom tarball Eugen.Hristev at microchip.com
2019-12-23 22:45 ` Thomas Petazzoni [this message]
2019-12-23 22:45 ` [Buildroot] [PATCH v2 1/2] configs/atmel: fix at91bootstrap custom tarball call function Thomas Petazzoni
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=20191223234525.107c5389@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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