All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: invalid sparse warnings ?
Date: Wed, 27 Nov 2013 10:01:31 +0100	[thread overview]
Message-ID: <5295B4EB.70609@broadcom.com> (raw)
In-Reply-To: <1385475973.4177.1.camel@jlt4.sipsolutions.net>

On 11/26/2013 03:26 PM, Johannes Berg wrote:
> On Tue, 2013-11-26 at 15:20 +0100, Arend van Spriel wrote:
>> Does some of you get these possibly invalid sparse warnings since 3.13-rc1?
>>
>> brcm80211/brcmfmac/bcmsdh.c:777:1: warning: symbol
>> '__ksymtab_brcmf_sdio_probe' was not declared. Should it be static?
>>
>> The function brcmf_sdio_probe() is exported using EXPORT_SYMBOL macro.
>> Maybe upgrade my sparse installment?
>
> See the sparse mailing list,
> http://www.spinics.net/lists/linux-sparse/msg03297.html

Thanks, Johannes

I should improve my google skills ;-)

Gr. AvS



      reply	other threads:[~2013-11-27  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 14:20 invalid sparse warnings ? Arend van Spriel
2013-11-26 14:26 ` Johannes Berg
2013-11-27  9:01   ` Arend van Spriel [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=5295B4EB.70609@broadcom.com \
    --to=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.