From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: "kbuild test robot" <fengguang.wu@intel.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [wireless-next:master 203/214] drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c:573:17: sparse: Using plain integer as NULL pointer
Date: Wed, 21 Nov 2012 18:59:57 +0100 [thread overview]
Message-ID: <50AD169D.3040206@broadcom.com> (raw)
In-Reply-To: <20121121141812.GB23606@thinkpad-t410>
On 11/21/2012 03:18 PM, Seth Forshee wrote:
> On Wed, Nov 21, 2012 at 03:24:13PM +0800, kbuild test robot wrote:
>> tree: git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git master
>> head: e2ff0498409af6f2023f91aba07b281e5e87ee15
>> commit: b353dda485038d5033b066cc946dfcf66afae128 [203/214] brcmsmac: Use debug macros for general error and debug statements
>>
>>
>> sparse warnings:
>>
>> + drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c:573:17: sparse: Using plain integer as NULL pointer
>
> There's actually a bug here. I'll send a patch.
So much for us reviewing your patches. The human eye can only see so
much, the mind can only process so much. Where would we be without
compilers. Using assemblers probably.
Gr. AvS
prev parent reply other threads:[~2012-11-21 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 7:24 [wireless-next:master 203/214] drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c:573:17: sparse: Using plain integer as NULL pointer kbuild test robot
2012-11-21 14:18 ` Seth Forshee
2012-11-21 17:59 ` 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=50AD169D.3040206@broadcom.com \
--to=arend@broadcom.com \
--cc=fengguang.wu@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=seth.forshee@canonical.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).