From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 5/5] arch/Config.in.sh: move BR2_ARCH_HAS_MMU_MANDATORY one level up
Date: Thu, 26 May 2022 11:46:00 +0200 [thread overview]
Message-ID: <8735gwr5if.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220419213450.887728-5-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Tue, 19 Apr 2022 23:34:49 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> Now that all SuperH cores have a MMU, and must use it, move back the
> select BR2_ARCH_HAS_MMU_MANDATORY one level up.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-26 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 21:34 [Buildroot] [PATCH 1/5] arch/Config.in.sh: fixup MMU selection Thomas Petazzoni via buildroot
2022-04-19 21:34 ` [Buildroot] [PATCH 2/5] arch/Config.in: remove BR2_ARCH_HAS_MMU_MANDATORY from BR2_aarch64* Thomas Petazzoni via buildroot
2022-04-19 21:34 ` [Buildroot] [PATCH 3/5] arch/Config.in.arm: re-organize MMU selection Thomas Petazzoni via buildroot
2022-05-18 20:24 ` Romain Naour
2022-05-18 21:35 ` Thomas Petazzoni via buildroot
2022-05-26 9:49 ` Peter Korsgaard
2022-04-19 21:34 ` [Buildroot] [PATCH 4/5] arch: drop support for SH2A Thomas Petazzoni via buildroot
2022-04-24 8:54 ` Yann E. MORIN
2022-04-19 21:34 ` [Buildroot] [PATCH 5/5] arch/Config.in.sh: move BR2_ARCH_HAS_MMU_MANDATORY one level up Thomas Petazzoni via buildroot
2022-05-26 9:46 ` Peter Korsgaard [this message]
2022-04-24 8:56 ` [Buildroot] [PATCH 1/5] arch/Config.in.sh: fixup MMU selection Yann E. MORIN
2022-05-26 9:44 ` Peter Korsgaard
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=8735gwr5if.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.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.