From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Raphael Silva <rapphil@gmail.com>
Cc: Larry.Finger@lwfinger.net, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtl8723au:type casting corrections
Date: Wed, 13 Aug 2014 17:42:20 +0200 [thread overview]
Message-ID: <wrfj7g2cgzvn.fsf@redhat.com> (raw)
In-Reply-To: <1407897034-28134-1-git-send-email-rapphil@gmail.com> (Raphael Silva's message of "Tue, 12 Aug 2014 23:30:34 -0300")
Raphael Silva <rapphil@gmail.com> writes:
> Type casting corrections in order to solve warnings of the sparce static analyser.
>
> Signed-off-by: Raphael Silva <rapphil@gmail.com>
> ---
> drivers/staging/rtl8723au/hal/usb_halinit.c | 4 ++--
> drivers/staging/rtl8723au/os_dep/ioctl_cfg80211.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
In the future, staging patches must have 'staging: rtl8723au: ....' in
the subject, and you need to CC devel@driverdev.osuosl.org as well.
Cheers,
Jes
>
> diff --git a/drivers/staging/rtl8723au/hal/usb_halinit.c b/drivers/staging/rtl8723au/hal/usb_halinit.c
> index b49bf33..969e4f3 100644
> --- a/drivers/staging/rtl8723au/hal/usb_halinit.c
> +++ b/drivers/staging/rtl8723au/hal/usb_halinit.c
> @@ -1228,9 +1228,9 @@ static void Hal_EfuseParsePIDVID_8723AU(struct rtw_adapter *pAdapter,
> } else {
> /* VID, PID */
> pHalData->EEPROMVID =
> - le16_to_cpu(*(u16 *)&hwinfo[EEPROM_VID_8723AU]);
> + le16_to_cpu(*(__le16 *)&hwinfo[EEPROM_VID_8723AU]);
> pHalData->EEPROMPID =
> - le16_to_cpu(*(u16 *)&hwinfo[EEPROM_PID_8723AU]);
> + le16_to_cpu(*(__le16 *)&hwinfo[EEPROM_PID_8723AU]);
> }
>
> MSG_8723A("EEPROM VID = 0x%4x\n", pHalData->EEPROMVID);
prev parent reply other threads:[~2014-08-13 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 2:30 [PATCH] rtl8723au:type casting corrections Raphael Silva
2014-08-13 15:42 ` Jes Sorensen [this message]
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=wrfj7g2cgzvn.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rapphil@gmail.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).