>
> I have added 1/2, since that one is a no-brainer. For 2/2, not so sure.
> Generally we try to avoid having sysfs file that aren't single value
> output. That isn't a super hard rule, but it is preferable.
>
> --
> Jens Axboe
>
Thanks Jens and sorry for the delay (extended vacation). Thanks
On 12/16/2016 11:54 AM, Stephen Bates wrote:
> Hi
>
> This series adds some more verbosity to the NVMe CMB sysfs entry.
>
> Jens I based this off v4.9 because for some reason your for-4.10/block
> is missing my original CMB commit (202021c1a63c6)?
>
> Stephen
>
> Stephen Bates (2):
> nvme :
Hi
This series adds some more verbosity to the NVMe CMB sysfs entry.
Jens I based this off v4.9 because for some reason your for-4.10/block
is missing my original CMB commit (202021c1a63c6)?
Stephen
Stephen Bates (2):
nvme : Use correct scnprintf in cmb show
nvme: improve cmb sysfs
On 12/16/2016 11:54 AM, Stephen Bates wrote:
> Hi
>
> This series adds some more verbosity to the NVMe CMB sysfs entry.
>
> Jens I based this off v4.9 because for some reason your for-4.10/block
> is missing my original CMB commit (202021c1a63c6)?
for-4.10/block was forked off v4.9-rc1, and
