public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <ynorov@caviumnetworks.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] bitmap: Drop unnecessary 0 check for u32 array operations
Date: Thu, 31 May 2018 17:47:49 +0300	[thread overview]
Message-ID: <20180531144749.GA6828@yury-thinkpad> (raw)
In-Reply-To: <20180531131914.44352-1-andriy.shevchenko@linux.intel.com>

On Thu, May 31, 2018 at 04:19:14PM +0300, Andy Shevchenko wrote:
> The nbits == 0 is safe to be supplied to the function body, so,
> remove unnecessary checks in bitmap_to_arr32() and bitmap_from_arr32().
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Indeed. Thanks for the catch.

> ---
>  lib/bitmap.c | 9 +--------
>  1 file changed, 1 insertion(+), 8 deletions(-)
> 
> diff --git a/lib/bitmap.c b/lib/bitmap.c
> index 58f9750e49c6..33e95cd359a2 100644
> --- a/lib/bitmap.c
> +++ b/lib/bitmap.c
> @@ -1132,14 +1132,10 @@ EXPORT_SYMBOL(bitmap_copy_le);
>   *	@buf: array of u32 (in host byte order), the source bitmap
>   *	@nbits: number of bits in @bitmap
>   */
> -void bitmap_from_arr32(unsigned long *bitmap, const u32 *buf,
> -						unsigned int nbits)
> +void bitmap_from_arr32(unsigned long *bitmap, const u32 *buf, unsigned int nbits)

This line is 81 characters length, and it will trigger checkpatch warning.
(But I'm OK with it.)

>  {
>  	unsigned int i, halfwords;
>  
> -	if (!nbits)
> -		return;
> -
>  	halfwords = DIV_ROUND_UP(nbits, 32);
>  	for (i = 0; i < halfwords; i++) {
>  		bitmap[i/2] = (unsigned long) buf[i];
> @@ -1163,9 +1159,6 @@ void bitmap_to_arr32(u32 *buf, const unsigned long *bitmap, unsigned int nbits)
>  {
>  	unsigned int i, halfwords;
>  
> -	if (!nbits)
> -		return;
> -
>  	halfwords = DIV_ROUND_UP(nbits, 32);
>  	for (i = 0; i < halfwords; i++) {
>  		buf[i] = (u32) (bitmap[i/2] & UINT_MAX);
> -- 
> 2.17.0

Acked-by: Yury Norov <ynorov@caviumnetworks.com>

  reply	other threads:[~2018-05-31 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 13:19 [PATCH v1] bitmap: Drop unnecessary 0 check for u32 array operations Andy Shevchenko
2018-05-31 14:47 ` Yury Norov [this message]
2018-06-14 12:03   ` Andy Shevchenko

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=20180531144749.GA6828@yury-thinkpad \
    --to=ynorov@caviumnetworks.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.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