From: Mike Rapoport <rppt@linux.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Christoph Hellwig <hch@infradead.org>,
"David S. Miller" <davem@davemloft.net>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] remove ARCH_SELECT_MEMORY_MODEL where it has no effect
Date: Thu, 16 May 2019 08:19:21 +0300 [thread overview]
Message-ID: <20190516051921.GC21366@rapoport-lnx> (raw)
In-Reply-To: <1556740577-4140-1-git-send-email-rppt@linux.ibm.com>
Andrew,
Can this go via the -mm tree?
On Wed, May 01, 2019 at 10:56:14PM +0300, Mike Rapoport wrote:
> Hi,
>
> For several architectures the ARCH_SELECT_MEMORY_MODEL has no real effect
> because the dependencies for the memory model are always evaluated to a
> single value.
>
> Remove the ARCH_SELECT_MEMORY_MODEL from the Kconfigs for these
> architectures.
>
> Mike Rapoport (3):
> arm: remove ARCH_SELECT_MEMORY_MODEL
> s390: remove ARCH_SELECT_MEMORY_MODEL
> sparc: remove ARCH_SELECT_MEMORY_MODEL
>
> arch/arm/Kconfig | 3 ---
> arch/s390/Kconfig | 3 ---
> arch/sparc/Kconfig | 3 ---
> 3 files changed, 9 deletions(-)
>
> --
> 2.7.4
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2019-05-16 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 19:56 [PATCH 0/3] remove ARCH_SELECT_MEMORY_MODEL where it has no effect Mike Rapoport
2019-05-01 19:56 ` [PATCH 1/3] arm: remove ARCH_SELECT_MEMORY_MODEL Mike Rapoport
2019-05-01 19:56 ` [PATCH 2/3] s390: " Mike Rapoport
2019-05-03 13:47 ` Heiko Carstens
2019-05-01 19:56 ` [PATCH 3/3] sparc: " Mike Rapoport
2019-05-16 5:19 ` Mike Rapoport [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=20190516051921.GC21366@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=schwidefsky@de.ibm.com \
--cc=sparclinux@vger.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 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 NNTP newsgroup(s).