From: Greg KH <gregkh@linuxfoundation.org>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: William Hubbs <w.d.hubbs@gmail.com>,
devel@driverdev.osuosl.org, Kirk Reiser <kirk@reisers.ca>,
speakup@linux-speakup.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Chris Brannon <chris@the-brannons.com>
Subject: Re: [PATCH v3 0/2] staging: checkpatch cleanups
Date: Thu, 16 Mar 2017 16:02:31 +0900 [thread overview]
Message-ID: <20170316070231.GA24453@kroah.com> (raw)
In-Reply-To: <CA+XqjF9cHvR=VnPmE3mqcKfyPJLL7_sMHWde_aWVG=WbT_rTMA@mail.gmail.com>
On Thu, Mar 16, 2017 at 12:02:25PM +0530, Arushi Singhal wrote:
>
>
> On Tue, Mar 14, 2017 at 3:35 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Mar 14, 2017 at 01:49:52AM +0530, Arushi Singhal wrote:
> > Improve readability by fixing multiple checkpatch.pl
> > issues in drivers.
> >
> > Arushi Singhal (2):
> > staging: speakup: identation should use tabs
> > staging: dvb-frontends: removed code in comments.
>
> What changed from v2?
>
> In this patch nothing is changed from v2 but it is a patch series so have to
> write v2 everywhere.
And everywhere you also need to say why it is v2, otherwise we have no
idea :(
thanks,
greg k-h
prev parent reply other threads:[~2017-03-16 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 20:19 [PATCH v3 0/2] staging: checkpatch cleanups Arushi Singhal
2017-03-13 20:19 ` [PATCH v3 1/2] staging: speakup: identation should use tabs Arushi Singhal
2017-03-13 22:05 ` Greg KH
2017-03-13 20:19 ` [PATCH v3 2/2] staging: dvb-frontends: removed code in comments Arushi Singhal
2017-03-13 22:05 ` [PATCH v3 0/2] staging: checkpatch cleanups Greg KH
[not found] ` <CA+XqjF9cHvR=VnPmE3mqcKfyPJLL7_sMHWde_aWVG=WbT_rTMA@mail.gmail.com>
2017-03-16 7:02 ` Greg KH [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=20170316070231.GA24453@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arushisinghal19971997@gmail.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).