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: <DC148C5AA1CEBA4E87973D432B1C2D88260262E2@P3PWEX4MB008.ex4.secureserver.net>
Date:	Wed, 5 Nov 2014 23:13:26 +0000
From:	Hartley Sweeten <HartleyS@...ionengravers.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Ian Abbott <abbotti@....co.uk>
CC:	"driverdev-devel@...uxdriverproject.org" 
	<driverdev-devel@...uxdriverproject.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/5] staging: comedi: split bus support into separate
 modules

On Wednesday, November 05, 2014 3:51 PM, Greg Kroah-Hartman wrote:
> On Fri, Oct 31, 2014 at 11:00:54PM +0000, Ian Abbott wrote:
>> On 31/10/14 22:53, Ian Abbott wrote:
>>> I like the idea of the core comedi module being separated from all the
>>> various buses. And other buses can be added easily without pulling extra
>>> dependencies into the core (e.g. for platform or spi devices).
>> 
>> And if this get's accepted, I'd like to complete the separation by moving
>> the PCI, USB and PCMCIA stuf out of the "comedidev.h" header into their own
>> headers, which obviously means small edits to most of the low-level drivers
>> to #include different headers. (But then, "comedi_pci.h" could #include
>> <linux/pci.h> for example.)
>
> Hartley, any objection to me applying this series?

No objections... Just questions... ;-)

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

Hartley
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ