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 1/2] staging: unisys: remove unused variable
Date: Wed, 11 Feb 2015 17:04:24 +0530 [thread overview]
Message-ID: <20150211113424.GA4856@sudip-PC> (raw)
In-Reply-To: <20150210063415.GB14158@kroah.com>
On Tue, Feb 10, 2015 at 02:34:15PM +0800, Greg Kroah-Hartman wrote:
> On Tue, Feb 10, 2015 at 10:50:06AM +0530, Sudip Mukherjee wrote:
> > >
> > > But as I've missed this in the past, nevermind, I'll take it as is. Can
> > > you resend your outstanding patches and I'll queue them up after
> > > 3.20-rc1 is out.
> > i will resend them now or should i send after the merge window closes?
>
> You can send patches any time, I'll batch them up and apply them to my
> trees at the proper time.
i have sent them as v2, i think i should have sent as [PATCH resend] :(
sudip
>
next prev parent reply other threads:[~2015-02-11 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 12:43 [PATCH 1/2] staging: unisys: remove unused variable Sudip Mukherjee
2015-02-06 12:43 ` [PATCH 2/2] staging: unisys: fix directory warning Sudip Mukherjee
2015-02-07 9:21 ` Greg Kroah-Hartman
2015-02-07 9:22 ` Greg Kroah-Hartman
2015-02-07 9:22 ` [PATCH 1/2] staging: unisys: remove unused variable Greg Kroah-Hartman
2015-02-08 11:01 ` Sudip Mukherjee
2015-02-09 21:35 ` Greg Kroah-Hartman
2015-02-10 5:20 ` Sudip Mukherjee
2015-02-10 6:34 ` Greg Kroah-Hartman
2015-02-10 7:03 ` Sudip Mukherjee
2015-02-11 11:34 ` Sudip Mukherjee [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-16 14:46 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=20150211113424.GA4856@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