From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Valentin Rothberg <valentinrothberg@gmail.com>,
linux390@de.ibm.com, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [linux-next] s390: Dump check for CONFIG_ZFCPDUMP
Date: Mon, 19 Jan 2015 13:15:28 +0100 [thread overview]
Message-ID: <20150119121528.GA5151@osiris> (raw)
In-Reply-To: <1421400905.15194.15.camel@x220>
On Fri, Jan 16, 2015 at 10:35:05AM +0100, Paul Bolle wrote:
> Commit 725908110a1f ("s390: add SMT support") added a check for
> CONFIG_ZFCPDUMP. But the Kconfig symbol ZFCPDUMP was removed in v3.16
> through commit bf28a5970de3 ("s390/dump: Remove CONFIG_ZFCPDUMP"). So
> this check will always evaluate to false. No one noticed probably
> because the code also checks for CONFIG_CRASH_DUMP which "also enables
> s390 zfcpdump".
>
> Dump the unneeded check.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Applied, thanks.
prev parent reply other threads:[~2015-01-19 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 9:35 [PATCH] [linux-next] s390: Dump check for CONFIG_ZFCPDUMP Paul Bolle
2015-01-19 12:15 ` 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=20150119121528.GA5151@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=pebolle@tiscali.nl \
--cc=schwidefsky@de.ibm.com \
--cc=valentinrothberg@gmail.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