public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	linux-kernel@vger.kernel.org, jdelvare@suse.de
Subject: Re: [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem
Date: Sat, 25 Apr 2015 15:29:32 +0530	[thread overview]
Message-ID: <20150425095932.GA6031@sudip-PC> (raw)
In-Reply-To: <20150425060929.GB3222@sudip-PC>

On Sat, Apr 25, 2015 at 11:39:29AM +0530, Sudip Mukherjee wrote:
> On Fri, Apr 24, 2015 at 07:37:02PM +0100, One Thousand Gnomes wrote:
> 
<snip>
> > Let me know when you have a set of patches you feel are good for testing
> > and I'll give them a go.
> This series of WIP is also good for testing.
well, this series will create some ghost parport in /sys/bus/parport,
which were being created while probing.
It has been fixed in my local tree and next WIP patch should be a fully
working one. But if you are testig this patchset then please use only
parport0.

regards
sudip


      reply	other threads:[~2015-04-25  9:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 13:52 [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem Sudip Mukherjee
2015-04-21 13:52 ` [PATCH v2 WIP 2/2] staging: panel: modify driver to use new parport device model Sudip Mukherjee
2015-04-23 15:18 ` [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem Dan Carpenter
2015-04-24  6:50   ` Sudip Mukherjee
2015-04-24  7:04     ` Dan Carpenter
2015-04-24  7:45       ` Sudip Mukherjee
2015-04-24  7:26     ` Greg KH
2015-04-24  7:38       ` Sudip Mukherjee
2015-04-24 18:37         ` One Thousand Gnomes
2015-04-25  6:09           ` Sudip Mukherjee
2015-04-25  9:59             ` Sudip Mukherjee [this message]

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=20150425095932.GA6031@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox