From: "D. Jeff Dionne" <djeffdionne@gmail.com>
To: Oscar Salvador <osalvador@suse.de>
Cc: glaubitz@physik.fu-berlin.de, geert+renesas@glider.be,
david@redhat.com, linux-sh@vger.kernel.org
Subject: Re: drop memory-hotplug on superH
Date: Fri, 17 May 2024 10:11:45 +0900 [thread overview]
Message-ID: <C7951B02-F75A-44C3-A3F4-F57EA05CDE94@gmail.com> (raw)
In-Reply-To: <ZkZruHmlKd7GaRHs@localhost.localdomain>
On May 17, 2024, at 05:25, Oscar Salvador <osalvador@suse.de> wrote:
Agree
> we no longer support memory-hotplug on 32bit platforms, so let us drop the
> memory-hotplug code for superH because it is a no-op at the moment.
> If there is ever a 64bit platform again, we shall re-implement it, and we
> shall do it on CONFIG_SPARSEMEM_VMEMMAP, since we plan do make memory-hotplug
> dependant on that, and drop support for CONFIG_SPARSEMEM &&
> !CONFIG_SPARSEMEM_VMEMMAP environments.
prev parent reply other threads:[~2024-05-17 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 20:25 drop memory-hotplug on superH Oscar Salvador
2024-05-16 20:30 ` David Hildenbrand
2024-05-17 1:11 ` D. Jeff Dionne [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=C7951B02-F75A-44C3-A3F4-F57EA05CDE94@gmail.com \
--to=djeffdionne@gmail.com \
--cc=david@redhat.com \
--cc=geert+renesas@glider.be \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-sh@vger.kernel.org \
--cc=osalvador@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).