linux-kernel - Re: [PATCH] staging: panel: remove duplicate code

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]

Date:	Tue, 7 Apr 2015 14:55:02 +0530
From:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	Willy Tarreau <willy@...a-x.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: panel: remove duplicate code

On Tue, Apr 07, 2015 at 11:49:30AM +0300, Dan Carpenter wrote:
> On Tue, Apr 07, 2015 at 01:55:01PM +0530, Sudip Mukherjee wrote:
> 
> I hadn't looked at this driver much before.  It sucks that
> parport_driver ->attach() functions can't fail... 

then maybe, we can change the code of parport. currently attach and
parport_register_driver never fails. we can modify it so that if attach
fails then parport_register_driver will also fail. will not be that much
difficult as it has been used only in 13 places.
your views ?

and since we are discussing parallel ports, few days back i saw one
post in ubuntuforums that his scanner is not working because of
lack of ppscsi.I mailed Tim Waugh, but he is not interested to work
with ppscsi anymore. parallel port scanners are almost a thing of the past
now. do you think it is worth that i pick up the code and modify
it for our latest kernel and submit to Greg ?

regards
sudip

> regards,
> dan carpenter
> 
--
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/