Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Chris Dimich <cdimich2188@gmail.com>
Cc: Gary Bisson <bisson.gary@gmail.com>,
	Refik Tuzakli <tuzakli.refik@gmail.com>,
	buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH 0/8] boundarydevices: update/add defconfigs
Date: Sat, 3 Aug 2024 20:25:14 +0200	[thread overview]
Message-ID: <20240803202514.6c56437c@windsurf> (raw)
In-Reply-To: <20240611180207.2138847-1-cdimich2188@gmail.com>

Hello Chris,

On Tue, 11 Jun 2024 11:01:59 -0700
Chris Dimich <cdimich2188@gmail.com> wrote:

> Chris Dimich (8):
>   board/boundarydevices: update boot scripts
>   board/boundarydevices: add i.MX 93 support to post-build.sh
>   configs/nitrogen*: bump kernel revision to f789d32c
>   configs/nitrogen*: bump u-boot revision to e3228228
>   configs/nitrogen8*: bump atf revision to d18357b7
>   configs/nitrogen8mm_defconfig: add SMARC support
>   configs/nitrogen8ulp: new defconfig
>   configs/nitrogen93: new defconfig

There were quite a few review comments or questions on multiple patches.

Also, in existing defconfigs, while bumping, it would be nice to enable
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y in those defconfigs.

Could you work on an updated version, and send a v2?

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

      parent reply	other threads:[~2024-08-03 18:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 18:01 [Buildroot] [PATCH 0/8] boundarydevices: update/add defconfigs Chris Dimich
2024-06-11 18:02 ` [Buildroot] [PATCH 1/8] board/boundarydevices: update boot scripts Chris Dimich
2024-07-11 22:43   ` Arnout Vandecappelle via buildroot
2024-06-11 18:02 ` [Buildroot] [PATCH 2/8] board/boundarydevices: add i.MX 93 support to post-build.sh Chris Dimich
2024-07-11 22:48   ` Arnout Vandecappelle via buildroot
2024-06-11 18:02 ` [Buildroot] [PATCH 3/8] configs/nitrogen*: bump kernel revision to f789d32c Chris Dimich
2024-06-11 18:02 ` [Buildroot] [PATCH 4/8] configs/nitrogen*: bump u-boot revision to e3228228 Chris Dimich
2024-06-11 18:02 ` [Buildroot] [PATCH 5/8] configs/nitrogen8*: bump atf revision to d18357b7 Chris Dimich
2024-06-11 18:02 ` [Buildroot] [PATCH 6/8] configs/nitrogen8mm_defconfig: add SMARC support Chris Dimich
2024-07-11 22:51   ` Arnout Vandecappelle via buildroot
2024-06-11 18:02 ` [Buildroot] [PATCH 7/8] configs/nitrogen8ulp: new defconfig Chris Dimich
2024-08-03 18:23   ` Thomas Petazzoni via buildroot
2024-06-11 18:02 ` [Buildroot] [PATCH 8/8] configs/nitrogen93: " Chris Dimich
2024-08-03 18:24   ` Thomas Petazzoni via buildroot
2024-08-03 18:25 ` 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=20240803202514.6c56437c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bisson.gary@gmail.com \
    --cc=cdimich2188@gmail.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.de_schampheleire@nokia.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tuzakli.refik@gmail.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