From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Benjamin Romer <benjamin.romer@unisys.com>,
David Kershner <david.kershner@unisys.com>,
sparmaintainer@unisys.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: unisys: uislib: uisqueue.c: rewrite of do_locked_client_insert
Date: Tue, 2 Sep 2014 11:24:02 -0700 [thread overview]
Message-ID: <20140902182402.GA12744@kroah.com> (raw)
In-Reply-To: <1409681795-23262-1-git-send-email-sudipm.mukherjee@gmail.com>
On Tue, Sep 02, 2014 at 11:46:35PM +0530, Sudip Mukherjee wrote:
> From: Sudip Mukherjee <sudip@vectorindia.org>
>
> removed unused variables
> fixed sparse warning of context imbalance in 'do_locked_client_insert'
> different lock contexts for basic block
>
> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> ---
>
> v1 of the patch of the patch just fixed the sparse warning.
> On suggestion of Dan Carpenter v2 is the total rewrite of the function.
> Two of the function arguments (interruptHandle,channelId) are also not used. Wanted to remove them as well ,
> but then thought maybe the original author have planned for some use of those variables.
>
> drivers/staging/unisys/uislib/uisqueue.c | 37 ++++++++------------------------
> 1 file changed, 9 insertions(+), 28 deletions(-)
>
> diff --git a/drivers/staging/unisys/uislib/uisqueue.c b/drivers/staging/unisys/uislib/uisqueue.c
> index 63dbe7c..acfa46d 100644
> --- a/drivers/staging/unisys/uislib/uisqueue.c
> +++ b/drivers/staging/unisys/uislib/uisqueue.c
> @@ -78,39 +78,20 @@ do_locked_client_insert(struct uisqueue_info *queueinfo,
> u64 interruptHandle, u8 *channelId)
> {
> unsigned long flags;
> - unsigned char queueWasEmpty;
> - unsigned int locked = 0;
> - unsigned int acquired = 0;
> u8 rc = 0;
>
> spin_lock_irqsave(lock, flags);
> - locked = 1;
> -
> if (!ULTRA_CHANNEL_CLIENT_ACQUIRE_OS(queueinfo->chan, channelId, NULL))
> - goto Away;
> -
> - acquired = 1;
> -
> - queueWasEmpty = visor_signalqueue_empty(queueinfo->chan, whichqueue);
> - if (!visor_signal_insert(queueinfo->chan, whichqueue, pSignal))
> - goto Away;
> - ULTRA_CHANNEL_CLIENT_RELEASE_OS(queueinfo->chan, channelId, NULL);
> - acquired = 0;
> -
> - queueinfo->packets_sent++;
> -
> - rc = 1;
> -Away:
> - if (acquired) {
> - ULTRA_CHANNEL_CLIENT_RELEASE_OS(queueinfo->chan, channelId,
> - NULL);
> - acquired = 0;
> - }
> - if (locked) {
> - spin_unlock_irqrestore((spinlock_t *) lock, flags);
> - locked = 0;
> + goto unlock;
> + visor_signalqueue_empty(queueinfo->chan, whichqueue);
> + /*visor_signal_insert() only return 0 or 1 */
Odd comment style (hint, you need a ' ' at the beginning...)
And why comment this at all?
thanks,
greg k-h
next prev parent reply other threads:[~2014-09-02 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 18:16 [PATCH v2] staging: unisys: uislib: uisqueue.c: rewrite of do_locked_client_insert Sudip Mukherjee
2014-09-02 18:24 ` Greg Kroah-Hartman [this message]
2014-09-02 18:54 ` Sudip Mukherjee
2014-09-03 8:40 ` Dan Carpenter
2014-09-03 8:59 ` Sudip Mukherjee
2014-09-03 9:20 ` Dan Carpenter
2014-09-03 14:43 ` Sudip Mukherjee
2014-09-03 15:41 ` Dan Carpenter
2014-09-03 16:26 ` 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=20140902182402.GA12744@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benjamin.romer@unisys.com \
--cc=david.kershner@unisys.com \
--cc=devel@driverdev.osuosl.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