lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 24 May 2016 23:45:54 -0400 From: David Kershner <david.kershner@...sys.com> To: <corbet@....net>, <tglx@...utronix.de>, <mingo@...hat.com>, <hpa@...or.com>, <david.kershner@...sys.com>, <gregkh@...uxfoundation.org>, <erik.arfvidson@...sys.com>, <timothy.sell@...sys.com>, <hofrat@...dl.org>, <dzickus@...hat.com>, <jes.sorensen@...hat.com>, <alexander.curtin@...sys.com>, <janani.rvchndrn@...il.com>, <sudipm.mukherjee@...il.com>, <prarit@...hat.com>, <david.binder@...sys.com>, <nhorman@...hat.com>, <dan.j.williams@...el.com>, <linux-kernel@...r.kernel.org>, <linux-doc@...r.kernel.org>, <driverdev-devel@...uxdriverproject.org>, <sparmaintainer@...sys.com> Subject: [PATCH 16/24] staging: unisys: visorbus: make visorbus_private.h function descriptions more kerneldoc-like From: David Binder <david.binder@...sys.com> Per audit feedback from Thomas Gleixner, function descriptions in visorbus_private.h now utilize a more kerneldoc-like formatting. The affected comments do not implement other kerneldoc requirements. Signed-off-by: David Binder <david.binder@...sys.com> Signed-off-by: David Kershner <david.kershner@...sys.com> --- drivers/staging/unisys/visorbus/visorbus_private.h | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/staging/unisys/visorbus/visorbus_private.h b/drivers/staging/unisys/visorbus/visorbus_private.h index 39edd20..f48f230 100644 --- a/drivers/staging/unisys/visorbus/visorbus_private.h +++ b/drivers/staging/unisys/visorbus/visorbus_private.h @@ -51,10 +51,11 @@ struct visorchipset_busdev_responders { void (*device_resume)(struct visor_device *p, int response); }; -/** Register functions (in the bus driver) to get called by visorchipset - * whenever a bus or device appears for which this guest is to be the - * client for. visorchipset will fill in <responders>, to indicate - * functions the bus driver should call to indicate message responses. +/** + * Register functions (in the bus driver) to get called by visorchipset + * whenever a bus or device appears for which this guest is to be the + * client for. visorchipset will fill in <responders>, to indicate + * functions the bus driver should call to indicate message responses. */ void visorchipset_register_busdev( -- 1.9.1
Powered by blists - more mailing lists