/freebsd/sbin/nvmecontrol/ |
H A D | perftest.c | 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days
|
H A D | reset.c | 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days
|
H A D | devlist.c | 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days
|
H A D | identify.c | 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days
|
H A D | firmware.c | 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days
|
H A D | nvmecontrol.c | 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days
|
H A D | logpage.c | 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days 821ef73c Tue Jul 09 21:14:15 GMT 2013 Jim Harris <jimharris@FreeBSD.org> Incorporate feedback from bde@ based on r252672 changes:
* Use 0/1 instead of sysexits. Man pages are confusing on this topic, but 0/1 is sufficient for nvmecontrol. * Use err function family where possible instead of fprintf/exit. * Fix some typing errors. * Clean up some error message inconsistencies.
Sponsored by: Intel Submitted by: bde (parts of firmware.c changes) MFC after: 3 days
|