From: John Garry <john.garry@huawei.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Johannes Thumshirn <jthumshirn@suse.de>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Hannes Reinecke <hare@suse.com>, Ming Lei <ming.lei@redhat.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi: core: Update SCSI_MQ_DEFAULT help text to match default
Date: Tue, 21 Aug 2018 14:08:48 +0100 [thread overview]
Message-ID: <690904cb-f9a0-ffe3-9ee7-1b76a6682031@huawei.com> (raw)
In-Reply-To: <20180821114407.18393-1-geert+renesas@glider.be>
On 21/08/2018 12:44, Geert Uytterhoeven wrote:
> The default was changed, but the help text was not updated.
>
> Fix grammar (s/the option/this option/) while at it.
>
> Fixes: d5038a13eca72fb2 ("scsi: core: switch to scsi-mq by default")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/scsi/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> index 8fc851a9e1162a56..a0491e11bd359499 100644
> --- a/drivers/scsi/Kconfig
> +++ b/drivers/scsi/Kconfig
> @@ -53,11 +53,11 @@ config SCSI_MQ_DEFAULT
> depends on SCSI
> ---help---
> This option enables the new blk-mq based I/O path for SCSI
It's arguably not 'new' either :)
> - devices by default. With the option the scsi_mod.use_blk_mq
> + devices by default. With this option the scsi_mod.use_blk_mq
> module/boot option defaults to Y, without it to N, but it can
> still be overridden either way.
>
> - If unsure say N.
> + If unsure say Y.
>
> config SCSI_PROC_FS
> bool "legacy /proc/scsi/ support"
>
next prev parent reply other threads:[~2018-08-21 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 11:44 [PATCH] scsi: core: Update SCSI_MQ_DEFAULT help text to match default Geert Uytterhoeven
2018-08-21 13:08 ` John Garry [this message]
2018-08-21 13:19 ` Ming Lei
2018-08-24 1:44 ` Martin K. Petersen
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=690904cb-f9a0-ffe3-9ee7-1b76a6682031@huawei.com \
--to=john.garry@huawei.com \
--cc=geert+renesas@glider.be \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.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).