Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Scott Fan <fancp2007@gmail.com>
Cc: buildroot@buildroot.org, Alexey Brodkin <alexey.brodkin@synopsys.com>
Subject: Re: [Buildroot] [PATCH 1/2] configs/cubieboard2: bump Linux to 6.11.6 and U-Boot to 2024.10
Date: Mon, 11 Nov 2024 22:29:26 +0100	[thread overview]
Message-ID: <20241111222926.079a1918@windsurf> (raw)
In-Reply-To: <20241108155434.1924823-1-fancp2007@gmail.com>

On Fri,  8 Nov 2024 23:54:31 +0800
Scott Fan <fancp2007@gmail.com> wrote:

> The boot.vfat image size is not enough now. The new zImage file
> is over 10M, so it is expanded to 16M.
> 
> Signed-off-by: Scott Fan <fancp2007@gmail.com>
> ---
>  board/cubietech/cubieboard2/genimage.cfg | 2 +-
>  configs/cubieboard2_defconfig            | 8 ++++----
>  2 files changed, 5 insertions(+), 5 deletions(-)

Thanks for your patch. However, we now require defconfigs to use hashes
to verify downloaded tarballs. Could you please enable
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y, and create the hashes using
utils/add-custom-hashes?

Thanks!

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-11-11 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 15:54 [Buildroot] [PATCH 1/2] configs/cubieboard2: bump Linux to 6.11.6 and U-Boot to 2024.10 Scott Fan
2024-11-08 15:54 ` [Buildroot] [PATCH 2/2] configs/cubieboard2: switch to use extlinux.conf Scott Fan
2024-11-11 21:31   ` Thomas Petazzoni via buildroot
2024-11-12 12:32   ` [Buildroot] [PATCH v2 " Scott Fan
2024-11-11 21:29 ` Thomas Petazzoni via buildroot [this message]
2024-11-12 12:32 ` [Buildroot] [PATCH v2 1/2] configs/cubieboard2: bump Linux to 6.11.7 and U-Boot to 2024.10 Scott Fan

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=20241111222926.079a1918@windsurf \
    --to=buildroot@buildroot.org \
    --cc=alexey.brodkin@synopsys.com \
    --cc=fancp2007@gmail.com \
    --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