From: Randy Dunlap <randy.dunlap@oracle.com>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
driverdevel <devel@driverdev.osuosl.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Brett Rudley <brudley@broadcom.com>,
Henry Ptasinski <henryp@broadcom.com>,
Nohee Ko <noheek@broadcom.com>
Subject: Re: linux-next: Tree for October 8 (staging/brcm80211)
Date: Sun, 10 Oct 2010 21:08:54 -0700 [thread overview]
Message-ID: <4CB28DD6.8000505@oracle.com> (raw)
In-Reply-To: <20101010202906.GA4900@kroah.com>
On 10/10/10 13:29, Greg KH wrote:
> On Sun, Oct 10, 2010 at 11:58:32AM -0700, Randy Dunlap wrote:
>> On Fri, 8 Oct 2010 16:15:52 +1100 Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> Changes since 20101007:
>>
>>
>>
>> drivers/staging/brcm80211/brcmfmac/dhd_linux.c:432: note: expected 'void *' but argument is of type 'sk_buff_data_t'
>> drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c:1337: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
>
> This is x86-64, right?
Yes.
>> drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c:2120: warning: initialization from incompatible pointer type
>> drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c:2121: warning: initialization from incompatible pointer type
>> drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c:2122: warning: initialization from incompatible pointer type
>> drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c:4035: warning: format '%d' expects type 'int', but argument 2 has type 'size_t'
>> drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c:4048: warning: format '%d' expects type 'int', but argument 2 has type 'size_t'
>
> I'll work on these.
>
> thanks,
>
> greg k-h
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2010-10-11 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 5:15 linux-next: Tree for October 8 Stephen Rothwell
2010-10-10 18:56 ` linux-next: Tree for October 8 (staging/intel_sst) Randy Dunlap
2010-10-10 20:29 ` Greg KH
2010-10-12 0:47 ` [PATCH -next] staging/intel_sst: include delay.h to fix build error Randy Dunlap
2010-10-10 18:58 ` linux-next: Tree for October 8 (staging/brcm80211) Randy Dunlap
2010-10-10 20:29 ` Greg KH
2010-10-11 4:08 ` Randy Dunlap [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=4CB28DD6.8000505@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=brudley@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=henryp@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=noheek@broadcom.com \
--cc=sfr@canb.auug.org.au \
/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).