From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755357AbbESMXH (ORCPT ); Tue, 19 May 2015 08:23:07 -0400 Received: from cantor2.suse.de ([195.135.220.15]:58086 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753994AbbESMXG (ORCPT ); Tue, 19 May 2015 08:23:06 -0400 Subject: Re: [PATCH v5 WIP 3/5] i2c-parport: define ports to connect From: Jean Delvare To: Dan Carpenter Cc: Sudip Mukherjee , Greg KH , One Thousand Gnomes , linux-kernel@vger.kernel.org In-Reply-To: <20150519112323.GN22558@mwanda> References: <1430907377-17147-1-git-send-email-sudipm.mukherjee@gmail.com> <1430907377-17147-3-git-send-email-sudipm.mukherjee@gmail.com> <20150519112323.GN22558@mwanda> Content-Type: text/plain; charset="UTF-8" Organization: Suse Linux Date: Tue, 19 May 2015 14:23:03 +0200 Message-ID: <1432038183.24979.66.camel@chaos.site> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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