From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/11] parport cleanup
Date: Tue, 22 Dec 2015 09:58:20 +0530 [thread overview]
Message-ID: <20151222042820.GB3250@sudip-pc> (raw)
In-Reply-To: <1446023500-21292-1-git-send-email-sudipm.mukherjee@gmail.com>
On Wed, Oct 28, 2015 at 02:41:29PM +0530, Sudip Mukherjee wrote:
> Hi Greg,
> A small series of checkpatch cleanup on parport. This is the first set.
> v1 had a problem with the From: line.
> Its only cleanup and no other change is done. All the patches are also
> sent along with this pull request for your convenience.
> This is my first pull request. Did i mess it up?
Hi Greg,
A gentle ping on this series.
regards
sudip
prev parent reply other threads:[~2015-12-22 4:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 9:11 [PATCH v2 00/11] parport cleanup Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 01/11] parport: fix a trivial typo Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 02/11] parport: remove trailing white space Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 03/11] parport: EXPORT_SYMBOL should follow function Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 04/11] parport: fix coding style Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 05/11] parport: code indent should use tabs Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 06/11] parport: quoted strings should not be split Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 07/11] parport: remove braces Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 08/11] parport: remove unnecessary out of memory message Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 09/11] parport: change style of NULL comparison Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 10/11] parport: remove unneeded space Sudip Mukherjee
2015-10-28 9:11 ` [PATCH v2 11/11] parport: avoid assignment in if Sudip Mukherjee
2015-12-22 4:28 ` 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=20151222042820.GB3250@sudip-pc \
--to=sudipm.mukherjee@gmail.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