linux-kernel - Re: [PATCH 00/12] Gigaset driver patches for 2.6.32

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1252286806.2139.1.camel@desktop>
Date:	Sun, 06 Sep 2009 18:26:46 -0700
From:	Daniel Walker <dwalker@...o99.com>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	davem@...emloft.net, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, i4ldeveloper@...tserv.isdn4linux.de,
	Hansjoerg Lipp <hjlipp@....de>
Subject: Re: [PATCH 00/12] Gigaset driver patches for 2.6.32

On Sun, 2009-09-06 at 20:58 +0200, Tilman Schmidt wrote:
> Dave,
> 
> following is a series of patches for the Gigaset driver which I would
> appreciate getting merged into kernel release 2.6.32.
> 
> The first one is a bugfix I had already submitted for 2.6.31 but which
> seems to have fallen through the cracks. Please disregard if it's
> already present your tree.
> 
> The next eight patches provide various small bugfixes, error handling
> and documentation improvements.
> 
> The final three patches add an alternative interface to the driver,
> connecting to the Kernel CAPI subsystem instead of the obsolescent
> ISDN4Linux subsystem. They have been presented on the i4ldeveloper
> mailing list and didn't draw any protests. (In fact, no comments at
> all. I'm determined to take that as a positive sign.)
> 
> Would you please take these into your net tree for 2.6.32.

patches 6,7,10, and 12 all have checkpatch errors. Could you fix those? 

Daniel

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