From: Christoph Hellwig <hch@infradead.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH v1 2/2] nvme: remove warning for shared ns when multipath=N
Date: Mon, 24 Jul 2023 09:53:17 -0700 [thread overview]
Message-ID: <ZL6sfR1MfTGsxnIj@infradead.org> (raw)
In-Reply-To: <20230719084147.16272-3-dwagner@suse.de>
On Wed, Jul 19, 2023 at 10:41:47AM +0200, Daniel Wagner wrote:
> The default value for the module parameter multipath is Y, thus the user
> has actively chosen to set multipath to N to trigger this warning with
> shared namespaces.
>
> There is at least one external mutlipathing module which conflict with
> the native multipathing feature (Dell's PowerPath module). In such setups
Why the fuck would we care? Out of tree modules don't matter, and
certainly no one should ever even dare to bother upstream with them.
Stop this crap.
prev parent reply other threads:[~2023-07-24 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 8:41 [PATCH v1 0/2] Remove CONFIG_NVME_MULTIPATH option Daniel Wagner
2023-07-19 8:41 ` [PATCH v1 1/2] nvme: drop multipath config option Daniel Wagner
2023-07-19 10:04 ` Keith Busch
2023-07-19 11:13 ` Daniel Wagner
2023-07-19 11:38 ` Keith Busch
2023-07-19 12:12 ` Daniel Wagner
2023-07-19 13:19 ` Hannes Reinecke
2023-07-24 16:51 ` Christoph Hellwig
2023-07-24 16:51 ` Christoph Hellwig
2023-07-25 6:05 ` Daniel Wagner
2023-07-26 13:11 ` Christoph Hellwig
2023-07-19 8:41 ` [PATCH v1 2/2] nvme: remove warning for shared ns when multipath=N Daniel Wagner
2023-07-24 16:53 ` Christoph Hellwig [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=ZL6sfR1MfTGsxnIj@infradead.org \
--to=hch@infradead.org \
--cc=dwagner@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).