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 v2] staging: unisys: uislib: uisqueue.c: rewrite of do_locked_client_insert
Date: Wed, 3 Sep 2014 11:40:38 +0300 [thread overview]
Message-ID: <20140903084038.GE6600@mwanda> (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>
I really would prefer if you just figured out your email settings so
this isn't needed. The From: header is mostly used for people
forwarding patches from other people. We have allowed people to use
the From header like this if they can't get their corporate email
configured properly but I try to discorage it. If everyone starts using
>From headers like this then it becomes a pain to deal with.
>
> 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>
> ---
>
This patch is much better and more interesting, but I still want some
more changes.
> 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.
In the kernel we don't put code in until we are ready to use it. Don't
worry about future changes. But on the other hand, don't remove the
parameters in this patch because that is doing too many changes in one
patch. It would have to be done in a follow on patch if you decide to
do it.
> - if (locked) {
> - spin_unlock_irqrestore((spinlock_t *) lock, flags);
> - locked = 0;
> + goto unlock;
> + visor_signalqueue_empty(queueinfo->chan, whichqueue);
Just remove this function. But mention it in the changelog in case
there are side effects.
> + /*visor_signal_insert() only return 0 or 1 */
Don't put obvious comments like this. A normal reader will assume that
this function is boolean based on how it is used.
> + if (visor_signal_insert(queueinfo->chan, whichqueue, pSignal) == 1) {
Don't put the == 1. In terms of English, 1 really is intended as
"success" and not the number one. Also don't test for == true or
== false.
if (foo) {
if (foo == true) {
These two statement *mean* the same thing in terms of English, but the
first one is simpler and less wordy.
regards,
dan carpenter
next prev parent reply other threads:[~2014-09-03 8:40 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
2014-09-02 18:54 ` Sudip Mukherjee
2014-09-03 8:40 ` Dan Carpenter [this message]
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=20140903084038.GE6600@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