From: Mike Rapoport <rppt@linux.ibm.com>
To: x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: [PATCH 0/2] x86/Kconfig: deprecate DISCONTIGMEM support for 32-bit
Date: Wed, 24 Apr 2019 16:24:10 +0300 [thread overview]
Message-ID: <1556112252-9339-1-git-send-email-rppt@linux.ibm.com> (raw)
Hi,
During the recent discussion [1] about DISCONTIGMEM being effectively
deprecated, Christoph suggested to mark it as BROKEN for x86-32.
These patches follow that suggestion and make SPARSEMEM the default for
X86_32 && NUMA and mark DISCONTIGMEM as BROKEN.
[1] https://lore.kernel.org/lkml/20190423071354.GB12114@infradead.org/
Mike Rapoport (2):
x86/Kconfig: make SPARSEMEM default for 32-bit
x86/Kconfig: deprecate DISCONTIGMEM support for 32-bit
arch/x86/Kconfig | 10 +++-------
1 file changed, 3 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2019-04-24 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 13:24 Mike Rapoport [this message]
2019-04-24 13:24 ` [PATCH 1/2] x86/Kconfig: make SPARSEMEM default for 32-bit Mike Rapoport
2019-04-24 14:19 ` Mel Gorman
2019-04-25 7:32 ` [tip:x86/mm] x86/Kconfig: Make SPARSEMEM default for 32-bit x86 tip-bot for Mike Rapoport
2019-04-24 13:24 ` [PATCH 2/2] x86/Kconfig: deprecate DISCONTIGMEM support for 32-bit Mike Rapoport
2019-04-24 14:20 ` Mel Gorman
2019-04-25 7:33 ` [tip:x86/mm] x86/Kconfig: Deprecate DISCONTIGMEM support for 32-bit x86 tip-bot for Mike Rapoport
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=1556112252-9339-1-git-send-email-rppt@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=bp@alien8.de \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
/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.