leandrof/linux
1
0
Fork 0
forked from Minki/linux
Code Issues Pull Requests Packages Projects Releases Wiki Activity

staging: unisys: include: Remove unused enum

Browse Source 
Removes unused enum that pertains to s-Par diagnostics capabilities.

Signed-off-by: David Binder <david.binder@unisys.com>
Signed-off-by: David Kershner <david.kershner@unisys.com>
Reviewed-by: Tim Sell <timothy.sell@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
David Binder 2017-09-27 13:14:42 -04:00 committed by Greg Kroah-Hartman
parent e27b10aa89
commit 66040f9104
1 changed files with 0 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
drivers/staging/unisys/include/visorbus.h
View File

@ -179,26 +179,6 @@ int visorbus_write_channel(struct visor_device *dev,
int visorbus_enable_channel_interrupts(struct visor_device *dev);
void visorbus_disable_channel_interrupts(struct visor_device *dev);
/*
* 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. Changes made
* to the enum, need to be reflected in s-Par.
*/
enum diag_severity {
DIAG_SEVERITY_VERBOSE = 0,
DIAG_SEVERITY_INFO = 1,
DIAG_SEVERITY_WARNING = 2,
DIAG_SEVERITY_ERR = 3,
DIAG_SEVERITY_PRINT = 4,
};
int visorchannel_signalremove(struct visorchannel *channel, u32 queue,
void *msg);
int visorchannel_signalinsert(struct visorchannel *channel, u32 queue,