From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem
Date: Fri, 24 Apr 2015 13:08:25 +0530 [thread overview]
Message-ID: <20150424073825.GF3489@sudip-PC> (raw)
In-Reply-To: <20150424072608.GA6494@kroah.com>
On Fri, Apr 24, 2015 at 09:26:08AM +0200, Greg KH wrote:
> On Fri, Apr 24, 2015 at 12:20:26PM +0530, Sudip Mukherjee wrote:
> > > What does ddev stand for? Anyway, it's probably better to call it
> > > bus_dev?
> > ok.
> > I think I will wait today for some comments from Greg and then send in
> > the v3 tomorrow.
>
> Don't wait for me, it's going to be a week or so at the earliest before
> I have a chance to look at this, sorry.
No problem. I will change what Dan has suggested and will
request Alan and Dean to check on their hardware as well (ofcourse if
they have time).
but finally it has to be you as you have to add it to your tree and I know
you can not modify your tree during the merge window.
regards
sudip
>
> greg "burried in email" k-h
next prev parent reply other threads:[~2015-04-24 7:38 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 [this message]
2015-04-24 18:37 ` One Thousand Gnomes
2015-04-25 6:09 ` Sudip Mukherjee
2015-04-25 9:59 ` Sudip Mukherjee
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=20150424073825.GF3489@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox