From: Trond Myklebust <trondmy@kernel.org>
To: Benjamin Coddington <bcodding@redhat.com>,
Anna Schumaker <anna@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 0/2] two fixes for pNFS SCSI device handling
Date: Fri, 22 Nov 2024 09:29:15 -0500 [thread overview]
Message-ID: <d7b2d246dfffb921f7d2c1e59fc0e6d847fcaf2f.camel@kernel.org> (raw)
In-Reply-To: <cover.1732279560.git.bcodding@redhat.com>
On Fri, 2024-11-22 at 07:47 -0500, Benjamin Coddington wrote:
> A bit late for v6.13 perhaps, but here are two fresh corrections for
> pNFS
> SCSI device handling, and some comments as requested by Christoph.
>
> On v2: add full commit subject in 1/2, change the caller in 2/2.
> On v3: add r-b for Chuck, tweak comments in 2/2.
>
> Benjamin Coddington (2):
> nfs/blocklayout: Don't attempt unregister for invalid block device
> nfs/blocklayout: Limit repeat device registration on failure
>
> fs/nfs/blocklayout/blocklayout.c | 15 ++++++++++++++-
> fs/nfs/blocklayout/dev.c | 6 ++----
> 2 files changed, 16 insertions(+), 5 deletions(-)
>
>
> base-commit: adc218676eef25575469234709c2d87185ca223a
Please make those patches be incremental against what is already in
linux-next.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2024-11-22 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 12:47 [PATCH v3 0/2] two fixes for pNFS SCSI device handling Benjamin Coddington
2024-11-22 12:47 ` [PATCH v3 1/2] nfs/blocklayout: Don't attempt unregister for invalid block device Benjamin Coddington
2024-11-22 12:47 ` [PATCH v3 2/2] nfs/blocklayout: Limit repeat device registration on failure Benjamin Coddington
2024-11-22 14:29 ` Trond Myklebust [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=d7b2d246dfffb921f7d2c1e59fc0e6d847fcaf2f.camel@kernel.org \
--to=trondmy@kernel.org \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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