From: David Kershner Date: Thu, 4 Jun 2015 13:22:46 +0000 (-0400) Subject: staging: unisys: Clean up diag_serverity enum X-Git-Tag: v4.2-rc1~88^2~302 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=c81e15a4b5622fa6f856435d424344828f6b3654;p=platform%2Fkernel%2Flinux-exynos.git staging: unisys: Clean up diag_serverity enum Get rid of unused values in the enum. Signed-off-by: David Kershner Signed-off-by: Benjamin Romer Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/staging/unisys/include/diagchannel.h b/drivers/staging/unisys/include/diagchannel.h index 82932c5..d2d3568 100644 --- a/drivers/staging/unisys/include/diagchannel.h +++ b/drivers/staging/unisys/include/diagchannel.h @@ -16,36 +16,28 @@ #ifndef _DIAG_CHANNEL_H_ #define _DIAG_CHANNEL_H_ -#include - #define MAX_MODULE_NAME_SIZE 128 /* Maximum length of module name... */ -#define MAX_ADDITIONAL_INFO_SIZE 256 /* Maximum length of any additional info - * accompanying event... +#define MAX_ADDITIONAL_INFO_SIZE 256 /* Maximum length of any additional + * info accompanying event... */ /* Levels of severity for diagnostic events, in order from lowest severity to -* highest (i.e. fatal errors are the most severe, and should always be logged, -* but info events rarely need to be logged except during debugging). The values -* DIAG_SEVERITY_ENUM_BEGIN and DIAG_SEVERITY_ENUM_END are not valid severity -* values. They exist merely to dilineate the list, so that future additions -* won't require changes to the driver (i.e. when checking for out-of-range -* severities in SetSeverity). The values DIAG_SEVERITY_OVERRIDE and -* DIAG_SEVERITY_SHUTOFF are not valid severity values for logging events but -* they are valid for controlling the amount of event data. This enum is also -* defined in DotNet\sParFramework\ControlFramework\ControlFramework.cs. If a -* change is made to this enum, they should also be reflected in that file. */ + * highest (i.e. fatal errors are the most severe, and should always be logged, + * but info events rarely need to be logged except during debugging). The + * values DIAG_SEVERITY_ENUM_BEGIN and DIAG_SEVERITY_ENUM_END are not valid + * severity values. They exist merely to dilineate the list, so that future + * additions won't require changes to the driver (i.e. when checking for + * out-of-range severities in SetSeverity). The values DIAG_SEVERITY_OVERRIDE + * and DIAG_SEVERITY_SHUTOFF are not valid severity values for logging events + * but they are valid for controlling the amount of event data. Changes made + * to the enum, need to be reflected in s-Par. + */ enum diag_severity { - DIAG_SEVERITY_ENUM_BEGIN = 0, - DIAG_SEVERITY_OVERRIDE = 0, DIAG_SEVERITY_VERBOSE = 0, DIAG_SEVERITY_INFO = 1, DIAG_SEVERITY_WARNING = 2, DIAG_SEVERITY_ERR = 3, - DIAG_SEVERITY_NONFATAL_ERR = 3, DIAG_SEVERITY_PRINT = 4, - DIAG_SEVERITY_FATAL_ERR = 4, - DIAG_SEVERITY_SHUTOFF = 5, - DIAG_SEVERITY_ENUM_END = 5 }; #endif