linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Benjamin Romer <benjamin.romer@unisys.com>,
	David Kershner <david.kershner@unisys.com>,
	devel@driverdev.osuosl.org, sparmaintainer@unisys.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] staging: unisys: remove unused variables
Date: Tue, 17 Mar 2015 12:51:41 +0530	[thread overview]
Message-ID: <20150317072105.GA6009@sudip-PC> (raw)
In-Reply-To: <20150316153519.GB12503@kroah.com>

On Mon, Mar 16, 2015 at 04:35:19PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Mar 12, 2015 at 11:00:09PM +0530, Sudip Mukherjee wrote:
> > these variable were being assigned some values but never reused.
> > 
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> > ---
> > 
> > v2: no change
> 
> Then why resend?
> 
> confused,
sorry for the confusion. but i was sending v2 of the series and this
patch from that series had no change. so in that case should i mark
the subject of this patch as [PATCH v2] or should it be just
[PATCH] ?

regards
sudip
> 
> greg k-h

      reply	other threads:[~2015-03-17  7:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 17:30 [PATCH v2 1/4] staging: unisys: remove unused variables Sudip Mukherjee
2015-03-12 17:30 ` [PATCH v2 2/4] staging: unisys: dev_t initialization Sudip Mukherjee
2015-03-16 15:36   ` Greg Kroah-Hartman
2015-03-24  8:14     ` Dan Carpenter
2015-03-12 17:30 ` [PATCH v2 3/4] staging: unisys: remove comparison Sudip Mukherjee
2015-03-12 17:30 ` [PATCH v2 4/4] staging: unisys: remove forward declarations Sudip Mukherjee
2015-03-16 15:35 ` [PATCH v2 1/4] staging: unisys: remove unused variables Greg Kroah-Hartman
2015-03-17  7:21   ` 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=20150317072105.GA6009@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=benjamin.romer@unisys.com \
    --cc=david.kershner@unisys.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparmaintainer@unisys.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).