All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, dan.carpenter@oracle.com
Subject: Re: [PATCH v2 1/2] parport: return of attach and parport_register_driver
Date: Wed, 8 Apr 2015 19:37:39 +0530	[thread overview]
Message-ID: <20150408140739.GA12490@sudip-PC> (raw)
In-Reply-To: <20150408134857.GA5585@kroah.com>

On Wed, Apr 08, 2015 at 03:48:57PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 08, 2015 at 07:00:16PM +0530, Sudip Mukherjee wrote:
> >  }
> 
> What really needs to happen is for the parport subsystem to move to the
> driver model, which I don't think ever happened way back during the 2.5
> development cycle.  When that happens, then you will not have code like
> this, and the drivers will work "properly"...
> 
> That's a much larger task, especially trying to do it without breaking
> anything along the way, but it's the "correct" thing to do.

and i guess since parport is orphan so no one is working on that
also, and maybe one more problem you all will be facing is lack
of systems with a parport. I do have systems with parallel port, so
let me try and see if i can do something about it. To start with,
I think I should go back to your LDD3-ch.14 for rest of the day.

regards
sudip

> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2015-04-08 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 13:30 [PATCH v2 1/2] parport: return of attach and parport_register_driver Sudip Mukherjee
2015-04-08 13:30 ` [PATCH v2 2/2] ppdev: return proper error values from attach Sudip Mukherjee
2015-04-08 13:48 ` [PATCH v2 1/2] parport: return of attach and parport_register_driver Greg Kroah-Hartman
2015-04-08 14:07   ` Sudip Mukherjee [this message]
2015-04-08 14:17 ` Dan Carpenter
2015-04-08 14:33   ` Sudip Mukherjee
2015-04-08 15:05     ` Dan Carpenter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150408140739.GA12490@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.