Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: sunil.m@techveda.org
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
	driverdev-devel@linuxdriverproject.org, karthik@techveda.org,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] staging: ccree: Fix bool comparison
Date: Tue, 17 Oct 2017 08:17:08 +1100	[thread overview]
Message-ID: <20171016211708.GM16106@eros> (raw)
In-Reply-To: <1508148491-11837-1-git-send-email-sunil.m@techveda.org>

On Mon, Oct 16, 2017 at 03:38:11PM +0530, sunil.m@techveda.org wrote:
> From: Suniel Mahesh <sunil.m@techveda.org>
> 
> Bool tests don't need comparisons.

This commit log could be a bit longer. You may like to read
Documentation/process/submitting-patches.rst (section 2).

> This fixes the following coccinelle warning:
> WARNING: Comparison of bool to 0/1
> 
> Signed-off-by: Suniel Mahesh <sunil.m@techveda.org>
> ---
> Note:
> - Patch was tested and built(ARCH=arm) on latest
>   linux-next.

Building is _not_ testing.

> - No build issues reported, however it was not
>   tested on real hardware.

This is implicit if you state 'builds on ARM'

> - Please discard this changeset, if this is not
>   helping the code look better.

This is implicit also ;)

> ---
>  drivers/staging/ccree/ssi_request_mgr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/ccree/ssi_request_mgr.c b/drivers/staging/ccree/ssi_request_mgr.c
> index 2e0df57..942afe2 100644
> --- a/drivers/staging/ccree/ssi_request_mgr.c
> +++ b/drivers/staging/ccree/ssi_request_mgr.c
> @@ -272,7 +272,7 @@ int send_request(
>  	unsigned int max_required_seq_len = (total_seq_len +
>  					((ssi_req->ivgen_dma_addr_len == 0) ? 0 :
>  					SSI_IVPOOL_SEQ_LEN) +
> -					((is_dout == 0) ? 1 : 0));
> +					(!is_dout ? 1 : 0));

Perhaps

-					((is_dout == 0) ? 1 : 0));
+					(is_dout ? 0 : 1)

Good luck,
Tobin.

  reply	other threads:[~2017-10-16 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 10:08 [PATCH] staging: ccree: Fix bool comparison sunil.m
2017-10-16 21:17 ` Tobin C. Harding [this message]
2017-10-18  2:10   ` [PATCH v2] " sunil.m
2017-10-18  2:33     ` Tobin C. Harding

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=20171016211708.GM16106@eros \
    --to=me@tobin.cc \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=karthik@techveda.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sunil.m@techveda.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