linux-kernel - RE: [PATCH 0/6] staging: comedi: gsc

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <DC148C5AA1CEBA4E87973D432B1C2D88261DB7C7@P3PWEX4MB008.ex4.secureserver.net>
Date:	Fri, 8 May 2015 17:06:10 +0000
From:	Hartley Sweeten <HartleyS@...ionengravers.com>
To:	Ian Abbott <abbotti@....co.uk>,
	"driverdev-devel@...uxdriverproject.org" 
	<driverdev-devel@...uxdriverproject.org>
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/6] staging: comedi: gsc_hpdi: some clean-ups

On Tuesday, May 05, 2015 10:47 AM, Ian Abbott wrote:
> Simplify (eliminate) the board type matching code, since only a single
> board type is supported.  Reformat the comments.  Fix the checkpatch
> issues.  Use a better module description string.
>
> 1) staging: comedi: gsc_hpdi: tidy up comments
> 2) staging: comedi: gsc_hpdi: remove multiple board type support
> 3) staging: comedi: gsc_hpdi: usleep_range is preferred over udelay
> 4) staging: comedi: gsc_hpdi: prefer using the BIT() macro
> 5) staging: comedi: gsc_hpdi: use PCI_DEVICE_SUB()
> 6) staging: comedi: gsc_hpdi: use a better MODULE_DESCRIPTION()
>
> drivers/staging/comedi/drivers/gsc_hpdi.c | 184 +++++++++++++-----------------
> 1 file changed, 80 insertions(+), 104 deletions(-)

Reviewed-by: H Hartley Sweeten <hsweeten@...ionengravers.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/