public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 10 Sep 2014 19:25:05 +0530	[thread overview]
Message-ID: <20140910135505.GA30082@sudip-PC> (raw)
In-Reply-To: <C97001BC43954D438ACB059713BA5CDFC97127E0E7@USEA-EXCH7.na.uis.unisys.com>

On Wed, Sep 10, 2014 at 08:29:26AM -0500, Romer, Benjamin M wrote:
> On Tue, 2014-09-09 at 16:11 +0530, Sudip Mukherjee wrote:
> > fixed sparse warning : context imbalance in 'resume_device'
> >                         unexpected unlock
> > this patch will generate warning from checkpatch for
> > lines over 80 character , but since those are user-visible strings
> > so it was not modified.
> > 
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> 
> I tested your changes, and this patch works fine. Thanks!
> 
> -- Ben
> 
> Acked-by: Benjamin Romer <benjamin.romer@unisys.com>
> Tested-by: Benjamin Romer <benjamin.romer@unisys.com>

thanks,
so after Greg K-H applies it then the patch to remove the last warning from this file.

thanks
sudip

  reply	other threads:[~2014-09-10 13:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 10:41 [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance Sudip Mukherjee
2014-09-10 13:29 ` Romer, Benjamin M
2014-09-10 13:55   ` Sudip Mukherjee [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-12 12:27 Sudip Mukherjee
2014-09-12 18:20 ` Ben Romer
2014-09-05  9:22 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
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

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=20140910135505.GA30082@sudip-PC \
    --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