From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rui Teng <rui.teng@linux.vnet.ibm.com>
Cc: Aditya Shankar <aditya.shankar@microchip.com>,
Ganesh Krishna <ganesh.krishna@microchip.com>,
devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/staging/wilc1000: fix sparse warning: right shift by bigger than source value
Date: Tue, 11 Jul 2017 19:04:49 +0200 [thread overview]
Message-ID: <20170711170449.GA30362@kroah.com> (raw)
In-Reply-To: <20170710085731.28397-1-rui.teng@linux.vnet.ibm.com>
On Mon, Jul 10, 2017 at 04:57:31PM +0800, Rui Teng wrote:
> This patch sets memory to zero directly to avoid unnecessary shift and
> bitwise operations on bool type, which can fix a sparse warning and also
> improve performance.
It does? How did you measure the performance impact? What was now
faster?
thanks,
greg k-h
>
> Signed-off-by: Rui Teng <rui.teng@linux.vnet.ibm.com>
> ---
> drivers/staging/wilc1000/host_interface.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/wilc1000/host_interface.c b/drivers/staging/wilc1000/host_interface.c
> index 2568dfc15181..036c5c19a016 100644
> --- a/drivers/staging/wilc1000/host_interface.c
> +++ b/drivers/staging/wilc1000/host_interface.c
> @@ -2416,10 +2416,9 @@ static void Handle_SetMulticastFilter(struct wilc_vif *vif,
> goto ERRORHANDLER;
>
> pu8CurrByte = wid.val;
> - *pu8CurrByte++ = (strHostIfSetMulti->enabled & 0xFF);
> - *pu8CurrByte++ = ((strHostIfSetMulti->enabled >> 8) & 0xFF);
> - *pu8CurrByte++ = ((strHostIfSetMulti->enabled >> 16) & 0xFF);
> - *pu8CurrByte++ = ((strHostIfSetMulti->enabled >> 24) & 0xFF);
> + memset(pu8CurrByte, 0, 4);
> + *pu8CurrByte = (strHostIfSetMulti->enabled & 0xFF);
> + pu8CurrByte += 4;
Are you sure enabled isn't larger than 8 bits?
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-11 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 8:57 [PATCH] drivers/staging/wilc1000: fix sparse warning: right shift by bigger than source value Rui Teng
2017-07-11 17:04 ` Greg Kroah-Hartman [this message]
2017-07-12 2:23 ` Rui Teng
2017-07-12 6:12 ` Greg Kroah-Hartman
2017-07-12 8:11 ` Joe Perches
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=20170711170449.GA30362@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rui.teng@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).