Re: [PATCH for-next v4 3/4] set pi_offset only when checksum type is not BLK_INTEGRITY_CSUM_NONE

To: Anuj Gupta <anuj20.g@xxxxxxxxxxx>
Subject: Re: [PATCH for-next v4 3/4] set pi_offset only when checksum type is not BLK_INTEGRITY_CSUM_NONE
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sun, 22 Jun 2025 22:30:14 -0700
Cc: vincent.fu@xxxxxxxxxxx, jack@xxxxxxx, anuj1072538@xxxxxxxxx, axboe@xxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, brauner@xxxxxxxxxx, hch@xxxxxxxxxxxxx, martin.petersen@xxxxxxxxxx, ebiggers@xxxxxxxxxx, adilger@xxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, joshi.k@xxxxxxxxxxx, linux-nvme@xxxxxxxxxxxxxxxxxxx, linux-scsi@xxxxxxxxxxxxxxx, gost.dev@xxxxxxxxxxx
In-reply-to: <20250618055153.48823-4-anuj20.g@samsung.com>

The Subject line is missing an "nvme: " prefix.

Otherwise looks good:

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH for-next v4 0/4] add ioctl to query metadata and protection info capabilities
  - From: Anuj Gupta
- [PATCH for-next v4 3/4] set pi_offset only when checksum type is not BLK_INTEGRITY_CSUM_NONE
  - From: Anuj Gupta