From: Keith Busch <kbusch@kernel.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
James Smart <james.smart@broadcom.com>,
Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/5] nvme-fabrics: short-circuit connect retries
Date: Wed, 1 May 2024 11:13:20 +0100 [thread overview]
Message-ID: <ZjIVwOazsC-miBK-@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20240430131928.29766-1-dwagner@suse.de>
On Tue, Apr 30, 2024 at 03:19:23PM +0200, Daniel Wagner wrote:
> I've splitted the last patch into the hopefully non controversial part 'do not
> retry when DNR is set' and the 'don't retry auth failures'. I hope we can get at
> least the first few patches in and have a lively discussion on the final patch
> at LSF.
I've dropped the previous series from the nvme-6.9 branch. This series
has been added to the newly created nvme-6.10 branch.
prev parent reply other threads:[~2024-05-01 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 13:19 [PATCH v7 0/5] nvme-fabrics: short-circuit connect retries Daniel Wagner
2024-04-30 13:19 ` [PATCH v7 1/5] nvmet: lock config semaphore when accessing DH-HMAC-CHAP key Daniel Wagner
2024-04-30 13:19 ` [PATCH v7 2/5] nvmet: return DHCHAP status codes from nvmet_setup_auth() Daniel Wagner
2024-04-30 13:23 ` Christoph Hellwig
2024-04-30 13:19 ` [PATCH v7 3/5] nvme: return kernel error codes for admin queue connect Daniel Wagner
2024-04-30 13:19 ` [PATCH v7 4/5] nvme-fabrics: short-circuit reconnect retries Daniel Wagner
2024-04-30 13:19 ` [PATCH v7 5/5] nvme: do not retry authentication failures Daniel Wagner
2024-05-01 10:27 ` Sagi Grimberg
2024-05-01 10:13 ` Keith Busch [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=ZjIVwOazsC-miBK-@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).