From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] drivers: nvme: Kconfig: pedantic cleanups
Date: Wed, 6 Mar 2019 19:51:53 +0000 [thread overview]
Message-ID: <SN6PR04MB4527FD956498AD3A5959470C86730@SN6PR04MB4527.namprd04.prod.outlook.com> (raw)
In-Reply-To: <1551897030-2219-1-git-send-email-info@metux.net>
On 3/6/19 10:31 AM, Enrico Weigelt, metux IT consult wrote:
> Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
> ---
> drivers/nvme/host/Kconfig | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/nvme/host/Kconfig b/drivers/nvme/host/Kconfig
> index 0f345e2..ce361c9 100644
> --- a/drivers/nvme/host/Kconfig
> +++ b/drivers/nvme/host/Kconfig
> @@ -17,10 +17,10 @@ config NVME_MULTIPATH
> bool "NVMe multipath support"
> depends on NVME_CORE
> ---help---
> - This option enables support for multipath access to NVMe
> - subsystems. If this option is enabled only a single
> - /dev/nvmeXnY device will show up for each NVMe namespaces,
> - even if it is accessible through multiple controllers.
> + This option enables support for multipath access to NVMe
> + subsystems. If this option is enabled only a single
> + /dev/nvmeXnY device will show up for each NVMe namespaces,
> + even if it is accessible through multiple controllers.
>
> config NVME_FABRICS
> tristate
>
Alignment looks good.
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
prev parent reply other threads:[~2019-03-06 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 18:30 Enrico Weigelt, metux IT consult
2019-03-06 19:51 ` Chaitanya Kulkarni [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=SN6PR04MB4527FD956498AD3A5959470C86730@SN6PR04MB4527.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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
all inboxes | Powered by JetHome®