[nvmewin] NVMe Windows DB Is UNLOCKED - Pushing Patch From Intel For LBA Range Type As Optional Feature

[Alex Chang]

I don't see any reasons not making the change you proposed to make it clear. As long as no objections received, will add that in next patch.

Thanks,
Alex

From: Freyensee, James P [mailto:james.p.freyensee at intel.com]
Sent: Tuesday, February 11, 2014 3:10 PM
To: Alex Chang
Subject: RE: [nvmewin] NVMe Windows DB Is UNLOCKED - Pushing Patch From Intel For LBA Range Type As Optional Feature

Is it also possible to get the following:

CommNvme.DeviceDesc = "Community NVME Storport Miniport"

to

CommNvme.DeviceDesc = "Community NVME 1.0.e Storport Miniport"

on the next patch applied please?



From: nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org> [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Alex Chang
Sent: Tuesday, February 11, 2014 2:26 PM
To: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: [nvmewin] NVMe Windows DB Is UNLOCKED - Pushing Patch From Intel For LBA Range Type As Optional Feature

Hi all,

Thank you, Carolyn, for the effort.
The patch had been updated to the source base and a new tag called "Patch#21_LBA_Range_Type_As_Optional_Feature" had been created under tags directory.  As suggested, I updated the DriverVer entry in nvme.inf to reflect the release date, Major/Minor release numbers, NVMe Specification Compliant revision (1.0 e) and patch number as below:
DriverVer=02/11/2014, 1.2.1014.21

Should you have any questions, please reply to the email listed below.

Thanks,
Alex

nvmewin mailing list
nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20140211/aa9e2b9f/attachment.html>