From: Randy Dunlap <rdunlap@xenotime•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
driverdevel <devel@driverdev•osuosl.org>,
gregkh@suse•de
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
forest@alittletooquiet•net, yunpeng.gao@intel•com,
vmehta@atheros•com
Subject: Re: linux-next: Tree for September 27 (staging: ath6kl, spectra, & vt6655)
Date: Mon, 27 Sep 2010 11:38:29 -0700 [thread overview]
Message-ID: <20100927113829.2928636a.rdunlap@xenotime.net> (raw)
In-Reply-To: <20100927162143.3a9c1efe.sfr@canb.auug.org.au>
On Mon, 27 Sep 2010 16:21:43 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100924:
drivers/staging/ath6kl/os/linux/ar6000_drv.c:1370:1: warning: "CONFIG_AR600x_BT_RESET_PIN" redefined
./include/generated/autoconf.h:419:1: warning: this is the location of the previous definition
drivers/staging/ath6kl/os/linux/ioctl.c:4673: warning: the frame size of 2052 bytes is larger than 1024 bytes
drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.c:288: error: 'struct mmc_host' has no member named 'max_hw_segs'
drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.c:289: error: 'struct mmc_host' has no member named 'max_hw_segs'
drivers/staging/spectra/ffsport.c:659: error: implicit declaration of function 'blk_queue_ordered'
drivers/staging/spectra/ffsport.c:659: error: 'QUEUE_ORDERED_DRAIN_FLUSH' undeclared (first use in this function)
drivers/staging/vt6655/device_main.c:3579: warning: the frame size of 1868 bytes is larger than 1024 bytes
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-09-27 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 6:21 linux-next: Tree for September 27 Stephen Rothwell
2010-09-27 18:38 ` Randy Dunlap [this message]
2010-09-27 19:28 ` linux-next: Tree for September 27 (staging: ath6kl, spectra, & vt6655) Vipin Mehta
2011-08-08 12:01 ` Geert Uytterhoeven
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=20100927113829.2928636a.rdunlap@xenotime.net \
--to=rdunlap@xenotime$(echo .)net \
--cc=devel@driverdev$(echo .)osuosl.org \
--cc=forest@alittletooquiet$(echo .)net \
--cc=gregkh@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=vmehta@atheros$(echo .)com \
--cc=yunpeng.gao@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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