summaryrefslogtreecommitdiff
path: root/fs/nfs
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2022-03-15 12:58:06 +0100
committerChristoph Hellwig <hch@lst.de>2022-03-16 09:47:01 +0100
commitb739e137052069c996ab8b3bc9c25be501ecc63b (patch)
treef404b3e85fb7cd43f8036f383eb74be191cdf342 /fs/nfs
parentda7837339641601f202f27515771dc0646083938 (diff)
downloadlinux-b739e137052069c996ab8b3bc9c25be501ecc63b.tar.gz
linux-b739e137052069c996ab8b3bc9c25be501ecc63b.tar.bz2
linux-b739e137052069c996ab8b3bc9c25be501ecc63b.zip
nvme: cleanup how disk->disk_name is assigned
They way how assigning the disk name and commenting on why it is done is split over core.c and multipath.c seems to be rather confusing. Now that ns_head->disk always exists we can do all the work in core.c and have a single big comment explaining the issues. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Keith Busch <kbusch@kernel.org> Reviewed-by: Sagi Grimberg <sagi@grimberg.me> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Diffstat (limited to 'fs/nfs')
0 files changed, 0 insertions, 0 deletions