[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150601054651.GA23300@sudip-PC>
Date: Mon, 1 Jun 2015 11:16:51 +0530
From: Sudip Mukherjee <sudipm.mukherjee@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Tim Waugh <tim@...erelk.net>, Jean Delvare <jdelvare@...e.de>,
Wolfram Sang <wsa@...-dreams.de>,
Willy Tarreau <willy@...a-x.org>,
Alan Cox <gnomes@...rguk.ukuu.org.uk>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
linux-i2c@...r.kernel.org
Subject: Re: [PATCH 0/6] use devicemodel with parport
On Mon, Jun 01, 2015 at 07:05:30AM +0900, Greg Kroah-Hartman wrote:
> On Wed, May 20, 2015 at 08:56:56PM +0530, Sudip Mukherjee wrote:
> > After 5 versions of WIP, finally a patch submission.
> > parport subsystem is now in the transition stage and supports the old
> > model and the new device model. 3 of the drivers have been converted
> > into new model and tested.
> > After other drivers are converted we can remove the old code from
> > parport.
>
> This looks good, very nice job.
Thanks, but its not me alone. Dan, Jean, Alan has helped me a lot in this.
>
> Are you going to continue to fix up the other drivers? I don't want us
> to have a half-converted subsystem in the kernel.
ofcourse yes. I also donot want to be a maintainer of half converted
subsystem. :)
i am thinking, after it is in the linux-next for a few days and seeing
any effects of these changes I will start with the other drivers.
and after all drivers are converted and that is also in next for sufficient
days I will start with the cleanup of the old codes.
And then there are some pending bugs in bugzilla. I am also planning to
add the code for epst in paride (i saw in many forums that people are
not able to use their scanner on latest kernels).
regards
sudip
>
> thanks,
>
> greg k-h
--
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