public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Paul Zimmerman <Paul.Zimmerman@synopsys.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	"balbi@ti.com" <balbi@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] usb: dwc2: gadget: sparse warning of context imbalance
Date: Fri, 17 Oct 2014 13:52:09 -0500	[thread overview]
Message-ID: <20141017185209.GY26260@saruman> (raw)
In-Reply-To: <A2CA0424C0A6F04399FB9E1CD98E0304844E345C@US01WEMBX2.internal.synopsys.com>

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

On Fri, Oct 17, 2014 at 06:50:19PM +0000, Paul Zimmerman wrote:
> > From: Sudip Mukherjee [mailto:sudipm.mukherjee@gmail.com]
> > Sent: Thursday, October 16, 2014 9:44 PM
> > 
> > sparse was giving the following warning:
> >         warning: context imbalance in 's3c_hsotg_ep_enable'
> > 	                - different lock contexts for basic block
> > 
> > we were returning ENOMEM while still holding the spinlock.
> > The sparse warning was fixed by releasing the spinlock before return.
> > 
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> > ---
> >  drivers/usb/dwc2/gadget.c | 7 +++++--
> >  1 file changed, 5 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
> > index 7b5856f..7f25527 100644
> > --- a/drivers/usb/dwc2/gadget.c
> > +++ b/drivers/usb/dwc2/gadget.c
> > @@ -2561,8 +2561,10 @@ static int s3c_hsotg_ep_enable(struct usb_ep *ep,
> >  			hs_ep->fifo_size = val;
> >  			break;
> >  		}
> > -		if (i == 8)
> > -			return -ENOMEM;
> > +		if (i == 8) {
> > +			ret = -ENOMEM;
> > +			goto error;
> > +		}
> >  	}
> > 
> >  	/* for non control endpoints, set PID to D0 */
> > @@ -2579,6 +2581,7 @@ static int s3c_hsotg_ep_enable(struct usb_ep *ep,
> >  	/* enable the endpoint interrupt */
> >  	s3c_hsotg_ctrl_epint(hsotg, index, dir_in, 1);
> > 
> > +error:
> >  	spin_unlock_irqrestore(&hsotg->lock, flags);
> >  	return ret;
> >  }
> 
> Acked-by: Paul Zimmerman <paulz@synopsys.com>

v3.18-rc or v3.19 ?

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-10-17 18:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17  4:44 [PATCH v3 1/2] usb: dwc2: gadget: sparse warning of context imbalance Sudip Mukherjee
2014-10-17  4:44 ` [PATCH v3 2/2] usb: dwc2: gadget: modify return statement Sudip Mukherjee
2014-10-17  9:02   ` David Laight
2014-10-17 10:03     ` Sudip Mukherjee
2014-10-17 18:10       ` Paul Zimmerman
2014-10-17 18:52   ` Paul Zimmerman
2014-10-17 18:50 ` [PATCH v3 1/2] usb: dwc2: gadget: sparse warning of context imbalance Paul Zimmerman
2014-10-17 18:52   ` Felipe Balbi [this message]
2014-10-17 19:05     ` Paul Zimmerman
2014-10-17 19:12       ` Felipe Balbi
2014-10-23 10:07       ` Sudip Mukherjee
2014-10-23 10:17         ` Greg Kroah-Hartman

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=20141017185209.GY26260@saruman \
    --to=balbi@ti.com \
    --cc=Paul.Zimmerman@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sudipm.mukherjee@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