public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 WIP 1/4] parport: add device-model to parport subsystem
Date: Sun, 3 May 2015 12:07:33 +0530	[thread overview]
Message-ID: <20150503063733.GA12351@sudip-PC> (raw)
In-Reply-To: <20150502162053.5dd0b1a8@endymion.delvare>

On Sat, May 02, 2015 at 04:20:53PM +0200, Jean Delvare wrote:
> Hi Sudip,
> 
> On Tue, 28 Apr 2015 17:00:20 +0530, Sudip Mukherjee wrote:
> > another WIP for your review. since this is not a formal patch for
> > applying so writing the comments here.
> 
> You should still provide a proper description as if the patch was ready
> to be committed. Ultimately the descriptions are going to be part of
> the commits, so they need to be reviewed too.
> 
> The history is good to have too for now, but it should go after the
> "---" separator, as it won't be part of the commit.
should i then send a v5 of WIP with proper commit message?
I will mention the WIP history as comments in my formal patch also.
And I guess, formal patch will take some time. After Alan has tested
I need to work on the documentation also.
> 
> > v4: use of is_parport() is introduced to check the type of device that
> > has been passed to probe or match_port.
> > 
<snip>
> > 
> > v2 had one more problem: it was creating some ghost parallel ports
> > during port probing. from v3 we have the use of parport_del_port
> > to remove registerd ports if probing has failed.
> 
> Spelling: "registered".
> 
> (As pointed out by ./scripts/checkpatch.pl - did you run it on each
> patch?)
while working on the code I will be checking with:
git diff | scripts/checkpatch.pl --strict -
so the change in the code is properly checkpatch tested.
and for formal submission of patches I will check again after writing
the commit message. But since this was just a WIP and not a formal
patch submission so I have not checked after writing the comments.

> 
> > 
<snip>
> > 
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> > ---
> >  drivers/parport/parport_pc.c |   4 +-
> >  drivers/parport/procfs.c     |  15 ++-
> >  drivers/parport/share.c      | 266 ++++++++++++++++++++++++++++++++++++++++---
> >  include/linux/parport.h      |  41 ++++++-
> >  4 files changed, 308 insertions(+), 18 deletions(-)
> > (...)
> 
> Patch tested, no functional regression found.
> 
> Tested-by: Jean Delvare <jdelvare@suse.de>
Thanks Jean.
Should i add your Tested-by: to the main patch and the patch
concerning the changes to i2c-parport?

regards
sudip
> 
> -- 
> Jean Delvare
> SUSE L3 Support

  reply	other threads:[~2015-05-03  6:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 11:30 [PATCH v4 WIP 1/4] parport: add device-model to parport subsystem Sudip Mukherjee
2015-04-28 11:30 ` [PATCH v4 WIP 2/4] i2c-parport: modify driver to use new parport device model Sudip Mukherjee
2015-05-03 13:33   ` Jean Delvare
2015-05-04  5:40     ` Sudip Mukherjee
2015-05-04  6:58       ` Jean Delvare
2015-05-04  7:24         ` Sudip Mukherjee
2015-05-04  9:14           ` Jean Delvare
2015-05-03 20:50   ` Jean Delvare
2015-04-28 11:30 ` [PATCH v4 WIP 3/4] paride: " Sudip Mukherjee
2015-04-28 11:30 ` [PATCH v4 WIP 4/4] staging: panel: " Sudip Mukherjee
2015-05-02 14:20 ` [PATCH v4 WIP 1/4] parport: add device-model to parport subsystem Jean Delvare
2015-05-03  6:37   ` Sudip Mukherjee [this message]
2015-05-03  7:56     ` Jean Delvare

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=20150503063733.GA12351@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