projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 525ec49) | patch
nvmet-tcp: don't fail maxr2t greater than 1
authorSagi Grimberg <sagi@grimberg.me>
Wed, 24 Apr 2019 18:53:16 +0000 (11:53 -0700)
committerChristoph Hellwig <hch@lst.de>
Thu, 25 Apr 2019 14:51:19 +0000 (16:51 +0200)
commit569b3d3db1aac8586a16df1745c9e5a99ff47253
tree851c4f43cf0e49504e011661cf933937efe74c91tree | snapshot
parent525ec495e021068aa8635a0e18ff60695f5b1f4fcommit | diff
nvmet-tcp: don't fail maxr2t greater than 1

The host may support it, but nothing prevents us from
sending a single r2t at a time like we do anyways.

Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
drivers/nvme/target/tcp.c diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)