From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
tfiga@chromium.org, paul.burton@mips.com,
m.szyprowski@samsung.com, egtvedt@samfundet.no,
linus.walleij@linaro.org, vgupta@synopsys.com,
mgorman@techsingularity.net, hch@lst.de, mina86@mina86.com,
robh@kernel.org, sboyd@codeaurora.org, paulus@ozlabs.org,
will.deacon@arm.com, tony@atomide.com, npiggin@gmail.com,
yamada.masahiro@socionext.com,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 08/20] s390/kconfig: Remove ARCH_WANTS_PROT_NUMA_PROT_NONE select
Date: Mon, 5 Feb 2018 07:56:51 +0100 [thread overview]
Message-ID: <20180205065651.GA4415@osiris> (raw)
In-Reply-To: <20180205012146.23981-9-ulfalizer@gmail.com>
On Mon, Feb 05, 2018 at 02:21:20AM +0100, Ulf Magnusson wrote:
> The ARCH_WANTS_PROT_NUMA_PROT_NONE symbol was removed by
> commit 6a33979d5bd7 ("mm: remove misleading ARCH_USES_NUMA_PROT_NONE"),
> but S390 still selects it.
>
> Remove the ARCH_WANTS_PROT_NUMA_PROT_NONE select from the S390 symbol.
>
> Discovered with the
> https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py
> script.
>
> Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
> ---
> arch/s390/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
Applied, thanks!
prev parent reply other threads:[~2018-02-05 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180205012146.23981-1-ulfalizer@gmail.com>
2018-02-05 1:21 ` [PATCH 08/20] s390/kconfig: Remove ARCH_WANTS_PROT_NUMA_PROT_NONE select Ulf Magnusson
2018-02-05 6:56 ` Heiko Carstens [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=20180205065651.GA4415@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=egtvedt@samfundet.no \
--cc=hch@lst.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mgorman@techsingularity.net \
--cc=mina86@mina86.com \
--cc=npiggin@gmail.com \
--cc=paul.burton@mips.com \
--cc=paulus@ozlabs.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=schwidefsky@de.ibm.com \
--cc=tfiga@chromium.org \
--cc=tony@atomide.com \
--cc=ulfalizer@gmail.com \
--cc=vgupta@synopsys.com \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.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 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).