All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jean-Christophe Bauduin via buildroot <buildroot@buildroot.org>
Cc: Jean-Christophe Bauduin <jean-christophe.bauduin@mind.be>,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] board/imx7d-sdb: bump linux to 6.6.58 and uboot to 2024.10
Date: Thu, 31 Oct 2024 19:04:46 +0100	[thread overview]
Message-ID: <20241031190446.149963ec@windsurf> (raw)
In-Reply-To: <20241030141811.1372499-1-jean-christophe.bauduin@mind.be>

Hello Jean-Christophe,

On Wed, 30 Oct 2024 15:18:11 +0100
Jean-Christophe Bauduin via buildroot <buildroot@buildroot.org> wrote:

> Bump the linux version from 6.6.21 to 6.6.58 and uboot from 2021.07 to 2024.10
> Signed-off-by: Jean-Christophe Bauduin <jean-christophe.bauduin@mind.be>

Thanks a lot for your patch!

A minor nit: there needs to be an empty line before your Signed-off-by
line.

But also, there is no need to repeat the commit title in the commit
message itself.

However, the bigger comment is that we are asking people who bump our
defconfigs to enable BR2_DOWNLOAD_FORCE_CHECK_HASHES=y. Could you have
a look at doing this? ./utils/add-custom-hashes will help you in
generating the hash files.

Thanks a lot!

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

  reply	other threads:[~2024-10-31 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 14:18 [Buildroot] [PATCH 1/1] board/imx7d-sdb: bump linux to 6.6.58 and uboot to 2024.10 Jean-Christophe Bauduin via buildroot
2024-10-31 18:04 ` Thomas Petazzoni via buildroot [this message]
2024-11-25 10:32 ` [Buildroot] [PATCH] " Jean-Christophe Bauduin via buildroot
2024-11-25 22:00   ` Julien Olivain

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=20241031190446.149963ec@windsurf \
    --to=buildroot@buildroot.org \
    --cc=festevam@gmail.com \
    --cc=jean-christophe.bauduin@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.