All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] support/testing/tests/fs/test_iso9660.py: use a more recent toolchain
Date: Tue, 19 Aug 2025 04:06:07 +0200	[thread overview]
Message-ID: <aae6c20414ae5826c36fd1fd4fdce2c1@free.fr> (raw)
In-Reply-To: <20250815103002.3871929-2-thomas.petazzoni@bootlin.com>

Hi Thomas,

On 15/08/2025 12:29, Thomas Petazzoni via buildroot wrote:
> The ISO9660 tests are currently using an old 2017 toolchain. Let's
> switch to a modern toolchain, which is regularly updated. Also, we use
> a toolchain based on glibc since grub2 doesn't build with recent
> uClibc toolchains.
> 
> It will work around build issues with syslinux.
> 
> Fixes:
> 
>   https://gitlab.com/buildroot.org/buildroot/-/jobs/10975828975
>   https://gitlab.com/buildroot.org/buildroot/-/jobs/10975828871
>   https://gitlab.com/buildroot.org/buildroot/-/jobs/10975828770
> 
> (Even though those should be fixed separately, as syslinux should
> continue to build with old compilers not supporting std=gnu17)
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

I applied this series to master, after a complete review and some more 
testing.

I also made few minor cosmetic changes in patch #3:
- fix patch #72 upstream link to point to the initial patch
   submission rather than a reply
- merge two _IGNORE_CVES blocks for patch #50 into a single one
- order _IGNORE_CVES blocks by numerical patch order
- order numerically the CVE list in commit log
- add a "Fixes:" tag in patch #74 since its commit log does not
   mention the CVE.

See:
https://gitlab.com/buildroot.org/buildroot/-/commit/ded3e0045aeeab226d2770fe8de522422c174434

Thanks a lot for this series!

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-08-19  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 10:29 [Buildroot] [PATCH 0/3] Backport security fixes to grub2 Thomas Petazzoni via buildroot
2025-08-15 10:29 ` [Buildroot] [PATCH 1/3] support/testing/tests/fs/test_iso9660.py: use a more recent toolchain Thomas Petazzoni via buildroot
2025-08-19  2:06   ` Julien Olivain via buildroot [this message]
2025-08-19  8:31     ` Thomas Petazzoni via buildroot
2025-08-21 19:21   ` Thomas Perale via buildroot
2025-08-15 10:29 ` [Buildroot] [PATCH 2/3] support/testing/tests/boot/test_grub.py: use glibc toolchain Thomas Petazzoni via buildroot
2025-08-21 19:21   ` Thomas Perale via buildroot
2025-08-15 10:30 ` [Buildroot] [PATCH 3/3] boot/grub2: add patches to fix numerous CVEs Thomas Petazzoni via buildroot
2025-08-21 19:21   ` Thomas Perale via buildroot

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=aae6c20414ae5826c36fd1fd4fdce2c1@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --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.