On 5/17/21 23:49, Christoph Hellwig wrote:

quoted

With this open coding in future we will have to maintain one extra macro
representing length for each new NIDT identifire that we will add.

I really don't see the point.  You remove one define per type, but
need to create a mapping table entry.  This adds (slightly) more code
and is less obvious.  Do you have any grand plans for which this is
a preparation?

Okay, we can drop this. No grand plans, I just thought open coding could
be avoided, but if that makes code complex no point.



_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme