Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Ludwig Kormann <ludwig.kormann@ict42.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] configs/icnova-a20-adb4006: Bump Linux and U-Boot version
Date: Fri, 11 Oct 2024 08:33:10 +0200	[thread overview]
Message-ID: <20241011083310.26cef6fd@windsurf> (raw)
In-Reply-To: <20241010091531.1943185-1-ludwig.kormann@ict42.de>

Hello Ludwig,

On Thu, 10 Oct 2024 11:15:30 +0200
Ludwig Kormann <ludwig.kormann@ict42.de> wrote:

> Bump version of Linux to 6.6.54 and U-Boot to 2024.10
> 
> Signed-off-by: Ludwig Kormann <ludwig.kormann@ict42.de>
> ---
>  configs/icnova-a20-adb4006_defconfig | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

Thanks a lot for your patch, which looks good. However, we're trying to
migrate all defconfigs to use hashes to check the Linux kernel and
U-Boot source code, by enabling BR2_DOWNLOAD_FORCE_CHECK_HASHES=y.
Could you also do this for this defconfig?

There is a tool ./utils/add-custom-hashes that helps in generating
those hashes. You can have a look at other defconfigs that use
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y to see how things are done.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-10-11  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  9:15 [Buildroot] [PATCH 1/2] configs/icnova-a20-adb4006: Bump Linux and U-Boot version Ludwig Kormann
2024-10-10  9:15 ` [Buildroot] [PATCH 2/2] configs/icnova-a20-adb4006: add uboot patch for reliable bootclk Ludwig Kormann
2024-10-11  6:34   ` Thomas Petazzoni via buildroot
2024-10-11  6:33 ` Thomas Petazzoni via buildroot [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=20241011083310.26cef6fd@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ludwig.kormann@ict42.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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