From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Aakash Hemadri <aakashhemadri123@gmail.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Bjorn Helgaas <bjorn@helgaas.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] staging: rtl8732bs: Fix sparse warnings
Date: Mon, 16 Aug 2021 20:48:48 +0200 [thread overview]
Message-ID: <22319634.U67b3Ei0OZ@localhost.localdomain> (raw)
In-Reply-To: <cover.1629135143.git.aakashhemadri123@gmail.com>
On Monday, August 16, 2021 7:35:05 PM CEST Aakash Hemadri wrote:
> This patchset fixes the below sparse warnings
>
> rtw_security.c:72:50: warning: incorrect type in assignment (different base
types)
> rtw_security.c:72:50: expected restricted __le32 [usertype]
> rtw_security.c:72:50: got unsigned int
>
> [...]
>
> This can be applied cleanly on next-20210816, and is compile tested.
This warnings have been fixed time ago against staging-testing:
please see commit aef1c966a364.
Thanks,
Fabio
> Please ignore the duplicate of this patchset, I did not CC staging.
> Message ID: <cover.1629134725.git.aakashhemadri123@gmail.com>
>
> Aakash Hemadri (2):
> staging: rtl8732bs: incorrect type in assignment
> staging: rtl8723bs: cast to restricted __le32
>
> drivers/staging/rtl8723bs/core/rtw_security.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
next prev parent reply other threads:[~2021-08-16 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 17:35 [PATCH 0/2] staging: rtl8732bs: Fix sparse warnings Aakash Hemadri
2021-08-16 17:35 ` [PATCH 1/2] staging: rtl8732bs: incorrect type in assignment Aakash Hemadri
2021-08-16 22:43 ` kernel test robot
2021-08-16 17:35 ` [PATCH 2/2] staging: rtl8723bs: fix cast to restricted __le32 Aakash Hemadri
2021-08-19 9:43 ` David Laight
2021-08-16 18:48 ` Fabio M. De Francesco [this message]
2021-08-18 5:58 ` [PATCH 0/2] staging: rtl8732bs: Fix sparse warnings Fabio M. De Francesco
-- strict thread matches above, loose matches on Subject: below --
2021-08-16 17:30 Aakash Hemadri
2021-08-17 17:54 ` Greg Kroah-Hartman
2021-08-17 19:10 ` Fabio M. De Francesco
2021-08-18 4:42 ` Aakash Hemadri
2021-08-18 4:40 ` Aakash Hemadri
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=22319634.U67b3Ei0OZ@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=aakashhemadri123@gmail.com \
--cc=bjorn@helgaas.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).