From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fengwei Tan <tfx2001@outlook.com>
Cc: buildroot@buildroot.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 0/3] support/scripts/gen-bootlin-toolchains: add missing BR2_USE_MMU dependencies
Date: Sat, 5 Sep 2026 20:51:09 +0200 [thread overview]
Message-ID: <apxkjfDG2NoMAlPW@windsurf> (raw)
In-Reply-To: <SY8P300MB0041EFD8D13BF20DAB3D61FCB5AB2@SY8P300MB0041.AUSP300.PROD.OUTLOOK.COM>
Hello,
On Sat, Aug 29, 2026 at 07:12:09PM +0800, Fengwei Tan wrote:
> Fengwei Tan (3):
> toolchain/toolchain-external/toolchain-external-bootlin: drop duplicate BR2_TOOLCHAIN_HAS_THREADS selections
> support/scripts/gen-bootlin-toolchains: add missing BR2_USE_MMU dependencies
> support/testing, toolchain/toolchain-external/toolchain-external-bootlin: regenerate after MMU dependency update
Thanks a lot, series applied!
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
prev parent reply other threads:[~2026-09-05 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 11:12 [Buildroot] [PATCH 0/3] support/scripts/gen-bootlin-toolchains: add missing BR2_USE_MMU dependencies Fengwei Tan
2026-08-29 11:12 ` [Buildroot] [PATCH 1/3] toolchain/toolchain-external/toolchain-external-bootlin: drop duplicate BR2_TOOLCHAIN_HAS_THREADS selections Fengwei Tan
2026-08-29 11:12 ` [Buildroot] [PATCH 2/3] support/scripts/gen-bootlin-toolchains: add missing BR2_USE_MMU dependencies Fengwei Tan
2026-08-29 11:12 ` [Buildroot] [PATCH 3/3] support/testing, toolchain/toolchain-external/toolchain-external-bootlin: regenerate after MMU dependency update Fengwei Tan
2026-09-05 18:51 ` 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=apxkjfDG2NoMAlPW@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=tfx2001@outlook.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 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.