mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bo YU <tsu.yubo@gmail.com>
Cc: adham.abozaeid@microchip.com, ajay.kathat@microchip.com,
	于波 <yuzibode@126.com>,
	"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: wilc1000: fix incorrect type in initializer
Date: Tue, 26 Feb 2019 12:59:35 +0100	[thread overview]
Message-ID: <20190226115935.GA18727@kroah.com> (raw)
In-Reply-To: <CAKq8=3L5tQNuB1EBjp4osZk83XBX48aWtPN7YiB0sbCg+j6q9g@mail.gmail.com>

On Tue, Feb 26, 2019 at 07:29:56PM +0800, Bo YU wrote:
> On Tue, Feb 26, 2019 at 2:00 PM Bo YU <tsu.yubo@gmail.com> wrote:
> 
> > Fix sparse warning following:
> >
> > drivers/staging/wilc1000/host_interface.c:444:49: warning: incorrect type
> > in initializer (different address spaces)
> > drivers/staging/wilc1000/host_interface.c:444:49:    expected struct
> > cfg80211_bss_ies const *ies
> > drivers/staging/wilc1000/host_interface.c:444:49:    got struct
> > cfg80211_bss_ies const [noderef] <asn:4> *ies
> >
> > Signed-off-by: Bo YU <tsu.yubo@gmail.com>
> > ---
> >  drivers/staging/wilc1000/host_interface.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/staging/wilc1000/host_interface.c
> > b/drivers/staging/wilc1000/host_interface.c
> > index cdcb52aec779..89ae22d40f71 100644
> > --- a/drivers/staging/wilc1000/host_interface.c
> > +++ b/drivers/staging/wilc1000/host_interface.c
> > @@ -441,7 +441,7 @@ void *wilc_parse_join_bss_param(struct cfg80211_bss
> > *bss,
> >         const u8 *tim_elm, *ssid_elm, *rates_ie, *supp_rates_ie;
> >         const u8 *ht_ie, *wpa_ie, *wmm_ie, *rsn_ie;
> >         int ret;
> > -       const struct cfg80211_bss_ies *ies = bss->ies;
> > +       const struct cfg80211_bss_ies *ies = rcu_dereference(bss->ies);
> >
> >         param = kzalloc(sizeof(*param), GFP_KERNEL);
> >         if (!param)
> > --
> > 2.11.0
> >
> > Hi,
> I do not Ccing wireless-list, Does it matter?

It would be nice to do that in the future.

      parent reply	other threads:[~2019-02-26 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26  6:00 Bo YU
     [not found] ` <CAKq8=3L5tQNuB1EBjp4osZk83XBX48aWtPN7YiB0sbCg+j6q9g@mail.gmail.com>
2019-02-26 11:59   ` Kroah-Hartman [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=20190226115935.GA18727@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adham.abozaeid@microchip.com \
    --cc=ajay.kathat@microchip.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®