linux-kernel - Re: [PATCH v5 WIP 3/5] i2c-parport: define ports to connect

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1432038183.24979.66.camel@chaos.site>
Date:	Tue, 19 May 2015 14:23:03 +0200
From:	Jean Delvare <jdelvare@...e.de>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	Sudip Mukherjee <sudipm.mukherjee@...il.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 WIP 3/5] i2c-parport: define ports to connect

Hi Dan,

Le Tuesday 19 May 2015 à 14:23 +0300, Dan Carpenter a écrit :
> On Wed, May 06, 2015 at 03:46:15PM +0530, Sudip Mukherjee wrote:
> > as of now i2c-parport was connecting to all the available parallel
> > ports. Lets limit that to maximum of 4 instances and at the same time
> > define which instance connects to which parallel port
> 
> So if you loaded this driver first then it was the only paraport driver
> which could run?  That's unfortunate.

This was indeed the case. The i2c-parport driver was for testing
evaluation boards and other home-brew electronics, so had a small count
of users, and the driver would always be loaded last anyway, so it was
not a problem in practice. Still I agree with the change as it makes
things cleaner and more flexible.

-- 
Jean Delvare
SUSE L3 Support

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