From 393363c5ec518210ad4ad66326d421b0adc55e07 Mon Sep 17 00:00:00 2001 From: Richard Laager Date: Sun, 14 Apr 2019 21:15:04 -0500 Subject: Consistently captialize GUID for features Reviewed-by: George Melikov Reviewed-by: Brian Behlendorf Signed-off-by: Richard Laager Closes #8626 --- module/zfs/zfeature.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'module/zfs/zfeature.c') diff --git a/module/zfs/zfeature.c b/module/zfs/zfeature.c index e6c1a5355..ed6ebcfc9 100644 --- a/module/zfs/zfeature.c +++ b/module/zfs/zfeature.c @@ -41,9 +41,9 @@ * spa_version() number. * * Each new on-disk format change will be given a uniquely identifying string - * guid rather than a version number. This avoids the problem of different + * GUID rather than a version number. This avoids the problem of different * organizations creating new on-disk formats with the same version number. To - * keep feature guids unique they should consist of the reverse dns name of the + * keep feature GUIDs unique they should consist of the reverse dns name of the * organization which implemented the feature and a short name for the feature, * separated by a colon (e.g. com.delphix:async_destroy). * @@ -95,11 +95,11 @@ * These objects are linked to by the following names in the pool directory * object: * - * 1) features_for_read: feature guid -> reference count + * 1) features_for_read: feature GUID -> reference count * Features needed to open the pool for reading. - * 2) features_for_write: feature guid -> reference count + * 2) features_for_write: feature GUID -> reference count * Features needed to open the pool for writing. - * 3) feature_descriptions: feature guid -> descriptive string + * 3) feature_descriptions: feature GUID -> descriptive string * A human readable string. * * All enabled features appear in either features_for_read or -- cgit v1.2.3