From: <Ajay.Kathat@microchip.com>
To: <tsu.yubo@gmail.com>, <Adham.Abozaeid@microchip.com>,
<gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <linux-wireless@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <yuzibode@126.com>
Subject: Re: [PATCH] staging: wilc1000: Fix incorrent type in assignment
Date: Tue, 26 Feb 2019 06:39:28 +0000 [thread overview]
Message-ID: <d71296ff-1de3-3af7-7ade-02e4ced08e7e@microchip.com> (raw)
In-Reply-To: <20190226032825.26171-1-tsu.yubo@gmail.com>
On 2/26/2019 8:58 AM, Bo YU wrote:
> The patch fixes following sparse warning:
>
> drivers/staging/wilc1000/host_interface.c:450:30: warning: incorrect type in assignment (different base types)
> drivers/staging/wilc1000/host_interface.c:450:30: expected restricted __le16 [usertype] beacon_period
> drivers/staging/wilc1000/host_interface.c:450:30: got unsigned short [usertype] beacon_interval
> drivers/staging/wilc1000/host_interface.c:451:25: warning: incorrect type in assignment (different base types)
> drivers/staging/wilc1000/host_interface.c:451:25: expected restricted __le16 [usertype] cap_info
> drivers/staging/wilc1000/host_interface.c:451:25: got unsigned short [usertype] capability
>
> Signed-off-by: Bo YU <tsu.yubo@gmail.com>
> ---
> I have no hardware to test it and just to compile it
Thanks for submitting the patch.
The correct way to fix above spare warning is by using cpu_to_le16()
while filing the information in ->beacon_period and ->cap_info because
wilc1000 module expects the data in _le_ byte order.
Please changes the below lines in host_interface.c and resubmit the patch.
param->beacon_period = bss->beacon_interval;
param->cap_info = bss->capability;
to
param->beacon_period = cpu_to_le16(bss->beacon_interval);
param->cap_info = cpu_to_le16(bss->capability);
> ---
> drivers/staging/wilc1000/host_interface.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/wilc1000/host_interface.c b/drivers/staging/wilc1000/host_interface.c
> index 50dc2dd942f5..cdcb52aec779 100644
> --- a/drivers/staging/wilc1000/host_interface.c
> +++ b/drivers/staging/wilc1000/host_interface.c
> @@ -106,10 +106,10 @@ struct wilc_join_bss_param {
> u8 ssid_terminator;
> u8 bss_type;
> u8 ch;
> - __le16 cap_info;
> + u16 cap_info;
> u8 sa[ETH_ALEN];
> u8 bssid[ETH_ALEN];
> - __le16 beacon_period;
> + u16 beacon_period;
> u8 dtim_period;
> u8 supp_rates[WILC_MAX_RATES_SUPPORTED + 1];
> u8 wmm_cap;
>
Regards,
Ajay
next prev parent reply other threads:[~2019-02-26 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 3:28 [PATCH] staging: wilc1000: Fix incorrent type in assignment Bo YU
2019-02-26 6:39 ` Ajay.Kathat [this message]
2019-02-26 7:27 ` YU Bo
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=d71296ff-1de3-3af7-7ade-02e4ced08e7e@microchip.com \
--to=ajay.kathat@microchip.com \
--cc=Adham.Abozaeid@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tsu.yubo@gmail.com \
--cc=yuzibode@126.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