From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Stefan Haberland <sth@linux.ibm.com>,
Jan Hoeppner <hoeppner@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390: Cleanup removed IOSCHED_DEADLINE
Date: Tue, 18 Feb 2020 13:17:13 +0100 [thread overview]
Message-ID: <20200218121713.GA3956@osiris> (raw)
In-Reply-To: <20200217165525.5187-1-krzk@kernel.org>
On Mon, Feb 17, 2020 at 05:55:25PM +0100, Krzysztof Kozlowski wrote:
> CONFIG_IOSCHED_DEADLINE is gone since commit f382fb0bcef4 ("block:
> remove legacy IO schedulers").
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Thanks! I'll leave it up to Stefan and Jan to decide what to do with this.
> ---
> drivers/s390/block/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/s390/block/Kconfig b/drivers/s390/block/Kconfig
> index a8682f69effc..1f06b19cb290 100644
> --- a/drivers/s390/block/Kconfig
> +++ b/drivers/s390/block/Kconfig
> @@ -26,7 +26,7 @@ config DASD
> def_tristate y
> prompt "Support for DASD devices"
> depends on CCW && BLOCK
> - select IOSCHED_DEADLINE
> + select MQ_IOSCHED_DEADLINE
> help
> Enable this option if you want to access DASDs directly utilizing
> S/390s channel subsystem commands. This is necessary for running
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-02-18 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:55 [PATCH] s390: Cleanup removed IOSCHED_DEADLINE Krzysztof Kozlowski
2020-02-18 12:17 ` Heiko Carstens [this message]
2020-02-18 15:18 ` Stefan Haberland
-- strict thread matches above, loose matches on Subject: below --
2020-01-30 19:25 Krzysztof Kozlowski
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=20200218121713.GA3956@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hoeppner@linux.ibm.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sth@linux.ibm.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 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.