From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fengwei Tan <tfx2001@outlook.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package: fix builds with $(PKG)_FLAT_STACKSIZE
Date: Sat, 22 Aug 2026 11:23:51 +0200 [thread overview]
Message-ID: <aolqYgE89zQA3YYz@windsurf> (raw)
In-Reply-To: <SY8P300MB0041DD7E48EB9FF02AB13414F8A22@SY8P300MB0041.AUSP300.PROD.OUTLOOK.COM>
Hello,
On Sat, Aug 22, 2026 at 05:14:39PM +0800, Fengwei Tan wrote:
> Since there is an ongoing discussion about removing noMMU support from
> the Linux kernel[1], I do not plan to upstream the HPMicro platform
> support there.
Meh, OK. I think this is not really the right move from the upstream
Linux kernel maintainers, but oh well.
> However, I will continue to submit any noMMU fixes to Buildroot whenever
> I find them.
If support for noMMU is dropped from upstream Linux, there is a fairly
high chance that we will follow along and at some point also drop
support for noMMU in Buildroot. It makes no sense to have support in
Buildroot if upstream Linux doesn't support noMMU.
Best regards,
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-08-22 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 18:17 [Buildroot] [PATCH] package: fix builds with $(PKG)_FLAT_STACKSIZE Fengwei Tan
2026-08-20 19:20 ` Thomas Petazzoni via buildroot
2026-08-21 17:26 ` Fengwei Tan
2026-08-21 20:24 ` Thomas Petazzoni via buildroot
2026-08-22 9:14 ` Fengwei Tan
2026-08-22 9:23 ` 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=aolqYgE89zQA3YYz@windsurf \
--to=buildroot@buildroot.org \
--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.