On 9/26/25 5:29 AM, Hannes Reinecke wrote:
On 9/26/25 11:00, Gustavo A. R. Silva wrote:
Hi,
Shouldn't this patch be removed from this series, since it's going to be
reverted anyways?
yes. To my understanding the FPIN patch series has been queued in
scsi-queue anyway, so it would be better to just send an incremental
patch on top of that.
Especially as Martin has already indicated that he will _not_ rebase
his tree.
This V10 patch series is based on nvme-v18.
I don't see the revert in scsi/6.18/scsi-queue yet
Best to just send this patch as a stand-alone patch, and then rebase
any not-yet-upstreamed patchsets on top of that.
I'd prefer to merge this patch with the FPIN-LI patch series. There is to good
way to test this field-spanning write fix w/out the FPIN_LI patches,
and the last time we cherry-picked and merged this fix it only led to confusion.
I think we should keep these together. I will add Gustavo's new fix to my V11
patch series.
/John
Cheers,
Hannes