On Fri, Nov 01, 2024 at 04:45:17PM -0600, Keith Busch wrote: > I've got the rest of the required logs and identifications implemented > in nvmet to support this. Cool! > There's one more issue, though, if we do > restrict the identify to >= 2.0 or 2.1. nvmet reports 1.3, and I suspect > there's a bit more work than just changing the value of NVMET_DEFAULT_VS > in order to comply with claiming that version. I don't think there were a lot of new mandatory requirements added that we didn't already do, or already we already ignored anyway, but it is worth a double check.
