From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>
Subject: Re: linux-next: Tree for May 22 (staging/)
Date: Fri, 22 May 2009 09:05:46 -0700 [thread overview]
Message-ID: <4A16CD5A.9050806@xenotime.net> (raw)
In-Reply-To: <20090522185110.3f95b03e.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20090521:
Saw these build warnings on x86_64:
drivers/staging/agnx/pci.c:64:3: warning: "/*" within comment
drivers/staging/agnx/pci.c:223:2: warning: "/*" within comment
drivers/staging/slicoss/slicoss.c:1875:warning: unused variable 'failure'
drivers/staging/stlc45xx/stlc45xx.c:2240: warning: 'struct ieee80211_if_conf' declared inside parameter list
drivers/staging/stlc45xx/stlc45xx.c:2240: warning: its scope is only this definition or declaration, which is probably not what you want
drivers/staging/stlc45xx/stlc45xx.c:2248: error: dereferencing pointer to incomplete type
drivers/staging/stlc45xx/stlc45xx.c:2248: error: dereferencing pointer to incomplete type
drivers/staging/stlc45xx/stlc45xx.c:2360: error: unknown field 'config_interface' specified in initializer
drivers/staging/stlc45xx/stlc45xx.c:2522: warning: format '%x' expects type 'unsigned int', but argument 3 has type 'long unsigned int'
drivers/staging/stlc45xx/stlc45xx.c:2524: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
drivers/staging/stlc45xx/stlc45xx.c:2524: warning: format '%x' expects type 'unsigned int', but argument 3 has type 'long unsigned int'
drivers/staging/rt3070/common/../../rt2870/common/../../rt2860/common/spectrum.c:1577: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
drivers/staging/rt3070/../rt2870/../rt2860/rt_linux.c:841: warning: format '%d' expects type 'int', but argument 3 has type 'long unsigned int'
There are also 2 outstanding patches for comedi build failures that need to
be applied so that more work can be done on comedi....
--
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
next prev parent reply other threads:[~2009-05-22 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 8:51 linux-next: Tree for May 22 Stephen Rothwell
2009-05-22 16:05 ` Randy Dunlap [this message]
2009-05-22 16:30 ` [PATCH -next] cpc-usb: fix PROC_FS dependency Randy Dunlap
2009-05-22 16:36 ` Randy Dunlap
2009-05-25 4:51 ` Sebastian Haas
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=4A16CD5A.9050806@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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.