dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <mwilck@suse.com>, Benjamin Marzinski <bmarzins@redhat.com>
Cc: Steven Schremmer <Steve.Schremmer@netapp.com>,
	NetApp RDAC team <ng-eseries-upstream-maintainers@netapp.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>,
	DM_DEVEL-ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 0/4] multipath-tools: add new NVMe devices to hwtable
Date: Sun, 5 Oct 2025 20:33:16 +0200	[thread overview]
Message-ID: <8b3cc8cc-052e-4ab5-a669-726e62f7a162@gmail.com> (raw)
In-Reply-To: <a8295cfe0ea955f6d0200ee04523cbd79eba6ca8.camel@suse.com>

On 9/22/25 8:56 PM, Martin Wilck wrote:

> I realize you set .no_path_retry = NO_PATH_RETRY_QUEUE for all devices.
> Should we use this for the generic NVMe device, too?

I played it safe, because most of them are using that value.
"generic" is fine as it is.

      reply	other threads:[~2025-10-05 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-13 13:02 [PATCH 0/4] multipath-tools: add new NVMe devices to hwtable Xose Vazquez Perez
2025-09-13 13:02 ` [PATCH v2 1/4] multipath-tools: remove checker from Huawei OceanStor NVMe Xose Vazquez Perez
2025-09-13 13:02 ` [PATCH 2/4] multipath-tools: add HITACHI VSP NVMe to hwtable Xose Vazquez Perez
2025-09-13 13:02 ` [PATCH 3/4] multipath-tools: add Infinidat InfiniBox " Xose Vazquez Perez
2025-09-13 13:02 ` [PATCH 4/4] multipath-tools: add VASTData Block Subsystem " Xose Vazquez Perez
2025-09-22 18:56 ` [PATCH 0/4] multipath-tools: add new NVMe devices " Martin Wilck
2025-10-05 18:33   ` Xose Vazquez Perez [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=8b3cc8cc-052e-4ab5-a669-726e62f7a162@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=Steve.Schremmer@netapp.com \
    --cc=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=mwilck@suse.com \
    --cc=ng-eseries-upstream-maintainers@netapp.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).