From: Kalle Valo <kvalo@kernel.org>
To: Srinivasan Raju <srini.raju@purelifi.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"edumazet\@google.com" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
"pabeni\@redhat.com" <pabeni@redhat.com>,
"open list\:NETWORKING DRIVERS \(WIRELESS\)"
<linux-wireless@vger.kernel.org>,
"open list\:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix le16_to_cpu warning for beacon_interval
Date: Fri, 29 Apr 2022 13:25:30 +0300 [thread overview]
Message-ID: <878rrodw4l.fsf@kernel.org> (raw)
In-Reply-To: <CWLP265MB3217B3A355529E36F6468A43E0FC9@CWLP265MB3217.GBRP265.PROD.OUTLOOK.COM> (Srinivasan Raju's message of "Fri, 29 Apr 2022 10:20:11 +0000")
Srinivasan Raju <srini.raju@purelifi.com> writes:
> Fixed the following warning
> drivers/net/wireless/purelifi/plfxlc/chip.c:36:31: sparse: expected unsigned short [usertype] beacon_interval
> drivers/net/wireless/purelifi/plfxlc/chip.c:36:31: sparse: got restricted __le16 [usertype]
The preferred style is this:
Fix the following sparse warnings:
drivers/net/wireless/purelifi/plfxlc/chip.c:36:31: sparse: expected unsigned short [usertype] beacon_interval
drivers/net/wireless/purelifi/plfxlc/chip.c:36:31: sparse: got restricted __le16 [usertype]
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Srinivasan Raju <srini.raju@purelifi.com>
> ---
> drivers/net/wireless/purelifi/plfxlc/chip.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
The subject should be:
[PATCH] plfxlc: fix le16_to_cpu warning for beacon_interval
> diff --git a/drivers/net/wireless/purelifi/plfxlc/chip.c b/drivers/net/wireless/purelifi/plfxlc/chip.c
> index a5ec10b66ed5..5d952ca07195 100644
> --- a/drivers/net/wireless/purelifi/plfxlc/chip.c
> +++ b/drivers/net/wireless/purelifi/plfxlc/chip.c
> @@ -30,10 +30,10 @@ int plfxlc_set_beacon_interval(struct plfxlc_chip *chip, u16 interval,
> {
> if (!interval ||
> (chip->beacon_set &&
> - le16_to_cpu(chip->beacon_interval) == interval))
> + chip->beacon_interval) == interval)
> return 0;
I think there's no need to use three lines anymore, two lines should be
enough:
if (!interval ||
(chip->beacon_set && chip->beacon_interval == interval))
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-04-29 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 10:20 [PATCH] Fix le16_to_cpu warning for beacon_interval Srinivasan Raju
2022-04-29 10:25 ` Kalle Valo [this message]
2022-04-29 11:16 ` Julian Calaby
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=878rrodw4l.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=srini.raju@purelifi.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).