diff options
| author | David Kershner <david.kershner@unisys.com> | 2017-08-22 13:27:11 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-08-22 15:12:51 -0700 |
| commit | a595a7ff8bb368c14830cf5384b8abffae20d1e9 (patch) | |
| tree | b95dedf3ae503d2333d80f2d128564327b84b1a0 /drivers/staging/unisys/include | |
| parent | 48401ac61fd7ca9d9bd9f033c85d2b78802c8973 (diff) | |
staging: unisys: include: Fix up comment style in visorbus.h
Visorbus.h had comments that did not have /* on its own line, this patch
makes it uniform.
Reviewed-by: Sameer Wadgaonkar <sameer.wadgaonkar@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>
Diffstat (limited to 'drivers/staging/unisys/include')
| -rw-r--r-- | drivers/staging/unisys/include/visorbus.h | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/drivers/staging/unisys/include/visorbus.h b/drivers/staging/unisys/include/visorbus.h index 354de7fdf4c0..097d4b3752ec 100644 --- a/drivers/staging/unisys/include/visorbus.h +++ b/drivers/staging/unisys/include/visorbus.h @@ -1,4 +1,5 @@ -/* visorbus.h +/* + * visorbus.h * * Copyright (C) 2010 - 2013 UNISYS CORPORATION * All rights reserved. @@ -54,8 +55,9 @@ struct visorchipset_state { /* Remaining bits in this 32-bit word are unused. */ }; -/** This struct describes a specific Supervisor channel, by providing its - * GUID, name, and sizes. +/* + * This struct describes a specific Supervisor channel, by providing its + * GUID, name, and sizes. */ struct visor_channeltype_descriptor { const guid_t guid; @@ -187,7 +189,8 @@ 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 +/* + * 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 |