[PATCH 0/6] staging fixes

From: Arnd Bergmann
Date: Thu Sep 30 2010 - 04:24:33 EST


My previous version of the first patch (staging: make new
character devices nonseekable) was untested and broke
compilation in multiple ways.

To make up for this, please take the fixed version
and some patches to fix basic problems in those
two drivers, as found by building with sparse.

Arnd

Arnd Bergmann (6):
staging: make new character devices nonseekable
stagin/ft1000-usb: fix unlocked_ioctl prototype
staging/ft1000-usb: fix build warnings
staging/ft1000-usb: fix problems found by sparse
staging/bcm: fix most build warnings
staging/bcm: add sparse annotations

drivers/staging/bcm/Adapter.h | 2 +-
drivers/staging/bcm/Bcmchar.c | 168 ++++++++++----------
drivers/staging/bcm/Bcmnet.c | 6 +-
drivers/staging/bcm/CmHost.c | 18 +-
drivers/staging/bcm/Debug.c | 2 +-
drivers/staging/bcm/HandleControlPacket.c | 2 +-
drivers/staging/bcm/IPv6Protocol.c | 4 +-
drivers/staging/bcm/InterfaceDld.c | 6 +-
drivers/staging/bcm/InterfaceIdleMode.c | 2 +-
drivers/staging/bcm/InterfaceIdleMode.h | 2 +-
drivers/staging/bcm/InterfaceInit.c | 31 ++--
drivers/staging/bcm/Ioctl.h | 8 +-
drivers/staging/bcm/LeakyBucket.c | 22 ++--
drivers/staging/bcm/Macros.h | 2 +-
drivers/staging/bcm/Misc.c | 20 ++-
drivers/staging/bcm/PHSDefines.h | 2 +-
drivers/staging/bcm/PHSModule.c | 2 +-
drivers/staging/bcm/Prototypes.h | 3 +-
drivers/staging/bcm/Qos.c | 8 +-
drivers/staging/bcm/Transmit.c | 4 +-
drivers/staging/bcm/led_control.c | 22 ++--
drivers/staging/bcm/nvm.c | 54 +++---
drivers/staging/ft1000/ft1000-usb/ft1000_chdev.c | 92 ++++++------
.../staging/ft1000/ft1000-usb/ft1000_download.c | 45 +++---
drivers/staging/ft1000/ft1000-usb/ft1000_hw.c | 95 +++++-------
drivers/staging/ft1000/ft1000-usb/ft1000_proc.c | 2 +-
drivers/staging/ft1000/ft1000-usb/ft1000_usb.c | 25 +---
drivers/staging/ft1000/ft1000-usb/ft1000_usb.h | 43 +++++-
28 files changed, 348 insertions(+), 344 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/