From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] parport: return of attach and parport_register_driver
Date: Wed, 8 Apr 2015 20:03:13 +0530 [thread overview]
Message-ID: <20150408143313.GA12753@sudip-PC> (raw)
In-Reply-To: <20150408141754.GT16501@mwanda>
On Wed, Apr 08, 2015 at 05:17:54PM +0300, Dan Carpenter wrote:
> On Wed, Apr 08, 2015 at 07:00:16PM +0530, Sudip Mukherjee wrote:
> > + if (attached) {
> > + list_add(&drv->list, &drivers);
> > + ret = 0;
> > + }
>
> I still think it would be nicer to create a do_attach() wrapper like I
> said earlier.
yes, after seeing your this code beside mine, your code looks more tidy
than mine. sorry, for not listening to you on the first place.
>
<snip>
> mutex_unlock(®istration_lock);
>
> if (!attached)
> return -ENODEV;
> return 0;
>
> The attach_driver_chain() function needs to be updated as well or it
> will break.
oops, i missed that function. but i didn't get any error?
ok, this is for those parallel ports which registers after our driver
registers.
But Greg wants to have parallel port changed into the device model,
so should i start with that task or shall we finalize this series so
that it can be applied for the timebeing?
regards
sudip
>
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2015-04-08 14:33 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
2015-04-08 14:17 ` Dan Carpenter
2015-04-08 14:33 ` Sudip Mukherjee [this message]
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=20150408143313.GA12753@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.