LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Aakash Hemadri <aakashhemadri123@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Bjorn Helgaas <bjorn@helgaas.com>,
	linux-staging@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] staging: rtl8732bs: Fix sparse warnings
Date: Tue, 17 Aug 2021 21:10:14 +0200	[thread overview]
Message-ID: <1648303.FNMM0ZEVYy@localhost.localdomain> (raw)
In-Reply-To: <YRv3w4y3r84mBjrU@kroah.com>

On Tuesday, August 17, 2021 7:54:11 PM CEST Greg Kroah-Hartman wrote:
> On Mon, Aug 16, 2021 at 11:00:41PM +0530, 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 series does not apply to my tree at all.  Please fix up and rebase
> and resubmit, after reading the mailing list archives for others that
> have attempted do do this type of work in the past for this issue.
> 
> It is not a trivial change that is needed...

Dear Greg,

As I've already pointed out in another message of this thread, your tree has 
already these sparse warnings fixed by me with commit aef1c966a364 (that 
you applied with a "much nicer!" comment).

So, when Aakash rebases against your current tree, he will not anymore see
those sparse warnings.

Thanks,

Fabio


> 
> thanks,
> 
> greg k-h
> 





  reply	other threads:[~2021-08-17 19:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 17:30 Aakash Hemadri
2021-08-16 17:30 ` [PATCH 1/2] staging: rtl8732bs: incorrect type in assignment Aakash Hemadri
2021-08-16 17:30 ` [PATCH 2/2] staging: rtl8723bs: fix cast to restricted __le32 Aakash Hemadri
2021-08-17 17:54 ` [PATCH 0/2] staging: rtl8732bs: Fix sparse warnings Greg Kroah-Hartman
2021-08-17 19:10   ` Fabio M. De Francesco [this message]
2021-08-18  4:42     ` Aakash Hemadri
2021-08-18  4:40   ` Aakash Hemadri
2021-08-16 17:35 Aakash Hemadri
2021-08-16 18:48 ` Fabio M. De Francesco
2021-08-18  5:58   ` Fabio M. De Francesco

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=1648303.FNMM0ZEVYy@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@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --subject='Re: [PATCH 0/2] staging: rtl8732bs: Fix sparse warnings' \
    /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

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).