From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: "Romer, Benjamin M" <Benjamin.Romer@unisys.com>
Cc: "Kershner, David A" <David.Kershner@unisys.com>,
*S-Par-Maintainer <SParMaintainer@unisys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance
Date: Mon, 8 Sep 2014 22:32:44 +0530 [thread overview]
Message-ID: <20140908170244.GA9392@fool> (raw)
In-Reply-To: <C97001BC43954D438ACB059713BA5CDFC97127E0E4@USEA-EXCH7.na.uis.unisys.com>
On Mon, Sep 08, 2014 at 11:48:44AM -0500, Romer, Benjamin M wrote:
> On Mon, 2014-09-08 at 22:08 +0530, Sudip Mukherjee wrote:
> > Hi Ben,
> > sorry to disturb you again. i got confused , which one is perfect one combined patch or
> > separate patches?
> >
> > thanks
> > sudip
>
> Two patches, as you preferred.
>
> -- Ben
>
>
ok. and if you get time can you please also have a look at :
[PATCH v4] staging: unisys: uislib: uisqueue.c: rewrite of do_locked_client_insert
Dan Carpenter has already reviwed it.
thanks
sudip
next prev parent reply other threads:[~2014-09-08 17:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 9:22 [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance Sudip Mukherjee
2014-09-08 15:57 ` Romer, Benjamin M
2014-09-08 16:27 ` Sudip Mukherjee
2014-09-08 16:30 ` Romer, Benjamin M
2014-09-08 16:38 ` Sudip Mukherjee
2014-09-08 16:48 ` Romer, Benjamin M
2014-09-08 17:02 ` Sudip Mukherjee [this message]
2014-09-08 17:06 ` Greg Kroah-Hartman
2014-09-08 17:10 ` Romer, Benjamin M
2014-09-08 17:24 ` Greg Kroah-Hartman
2014-09-08 17:33 ` Romer, Benjamin M
-- strict thread matches above, loose matches on Subject: below --
2014-09-09 10:41 Sudip Mukherjee
2014-09-10 13:29 ` Romer, Benjamin M
2014-09-10 13:55 ` Sudip Mukherjee
2014-09-12 12:27 Sudip Mukherjee
2014-09-12 18:20 ` Ben Romer
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=20140908170244.GA9392@fool \
--to=sudipm.mukherjee@gmail.com \
--cc=Benjamin.Romer@unisys.com \
--cc=David.Kershner@unisys.com \
--cc=SParMaintainer@unisys.com \
--cc=devel@driverdev.osuosl.org \
--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