From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boot/uboot: add hash for 2012.07
Date: Tue, 28 Apr 2015 10:03:57 +0200 [thread overview]
Message-ID: <20150428100357.634cf24c@free-electrons.com> (raw)
In-Reply-To: <20150426213341.GI4809@free.fr>
Dear Yann E. MORIN,
On Sun, 26 Apr 2015 23:33:41 +0200, Yann E. MORIN wrote:
> > The problem indeed exists, but this is not the right solution. The
> > right solution is to use BR_NO_CHECK_HASH_FOR. Yann, can you look at
> > all the packages that may use custom versions (U-Boot, Barebox,
> > kernel, etc.) and do the necessary BR_NO_CHECK_HASH_FOR handling?
>
> I'll have a look.
Any updates on this? One quick option I see is to remove uboot.hash for
now.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-28 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 19:56 [Buildroot] [PATCH] boot/uboot: add hash for 2012.07 Vincent Stehle
2015-04-26 20:27 ` Thomas Petazzoni
2015-04-26 21:33 ` Yann E. MORIN
2015-04-28 8:03 ` Thomas Petazzoni [this message]
2015-04-28 9:52 ` Yann E. MORIN
2015-04-28 14:58 ` 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=20150428100357.634cf24c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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