Peter Rajnoha 028ff30947 cleanup: use helper macros to get reserved value from values.h for vg_mda_copies and lv_read_ahead fields ... Avoid making a copy of the keyword which is already registered in values.h for "unmanaged" (vg_mda_copies field) and "auto" reserved value (lv_read_ahead field). Also use helper macros to handle these reserved - this is the correct approach - just do not copy the same thing again and do not mix it! The GET_FIELD_RESERVED_VALUE and GET_FIRST_RESERVED_NAME macros guarantees this - use it! In addition to that, rename reserved values: vg_mda_copies --> vg_mda_copies_unmanaged lv_read_ahead --> lv_read_ahead_auto So the field reserved values follows this scheme: "<field_name>_<reserved_value_name>". The same applies for type reserved values with this scheme: "<report type name in lowercase>_<reserved_value_name>" Add a comment about this scheme for others to follow as well when adding new fields and their reserved values. This makes it a bit easier to read the code then.		2014-12-18 15:07:46 +01:00
..
columns-devtypes.h	reporting: Add devtypes command.	2013-09-18 01:09:15 +01:00
columns.h	report: Add cache_policy and cache_settings (LV) segment fields.	2014-12-17 14:43:12 +01:00
properties.c	report: Add cache_policy and cache_settings (LV) segment fields.	2014-12-17 14:43:12 +01:00
properties.h	report: select: refactor: move str_list to libdm	2014-06-17 16:27:20 +02:00
report.c	cleanup: use helper macros to get reserved value from values.h for vg_mda_copies and lv_read_ahead fields	2014-12-18 15:07:46 +01:00
report.h	report: add new LVSSTATUS and SEGSSTATUS report type	2014-11-11 08:53:28 +01:00
values.h	cleanup: use helper macros to get reserved value from values.h for vg_mda_copies and lv_read_ahead fields	2014-12-18 15:07:46 +01:00