From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Benjamin Romer <benjamin.romer@unisys.com>,
David Kershner <david.kershner@unisys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, sparmaintainer@unisys.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: unisys: uislib: uisqueue.c: fixed sparse warning of context imbalance
Date: Tue, 2 Sep 2014 18:23:27 +0300 [thread overview]
Message-ID: <20140902152327.GG6549@mwanda> (raw)
In-Reply-To: <20140902151427.GA11966@sudip-PC>
On Tue, Sep 02, 2014 at 08:44:27PM +0530, Sudip Mukherjee wrote:
> On Tue, Sep 02, 2014 at 05:05:32PM +0300, Dan Carpenter wrote:
> > On Tue, Sep 02, 2014 at 04:39:47PM +0530, Sudip Mukherjee wrote:
> > > fixed sparse warning : context imbalance in 'do_locked_client_insert'
> > > different lock contexts for basic block
> > >
> > > spin_unlock_irqrestore is called at a later stage before returning
> > > from the function if locked is 1.
> > >
> > > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> >
> > This doesn't match the email address you are using.
> >
>
> for all my patch the Signed-off email address is different from the From email address.
> I am not sure if I should do that, but since no one pointed it out so I guessed it is ok.
Sign-off-by are like signing a legal document that you didn't steal
copyright code. We like to check that they match up with the email
sending the patch.
regards,
dan carpenter
next prev parent reply other threads:[~2014-09-02 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 11:09 [PATCH] staging: unisys: uislib: uisqueue.c: fixed sparse warning of context imbalance Sudip Mukherjee
2014-09-02 14:05 ` Dan Carpenter
2014-09-02 15:14 ` Sudip Mukherjee
2014-09-02 15:23 ` Dan Carpenter [this message]
2014-09-02 16:58 ` 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=20140902152327.GG6549@mwanda \
--to=dan.carpenter@oracle.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 \
--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