- Oct 06, 2010
-
-
Henry Ptasinski authored
Remove assertions on the size of several structures. These structures are never used anywhere. Signed-off-by:
Henry Ptasinski <henryp@broadcom.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Henry Ptasinski authored
Remove the wl_assoc_info_t structure. It's never used, and depends on structures defined in other header files that can now also be cleaned up. Signed-off-by:
-
Jason Cooper authored
Signed-off-by:
Jason Cooper <jason@lakedaemon.net> Acked-by:
-
Jason Cooper authored
Signed-off-by:
-
Jason Cooper authored
Signed-off-by:
-
Jason Cooper authored
Signed-off-by:
-
Jason Cooper authored
Signed-off-by:
-
Jason Cooper authored
Signed-off-by:
-
Jason Cooper authored
Signed-off-by:
-
Jason Cooper authored
Signed-off-by:
-
Jason Cooper authored
Signed-off-by:
-
Arnd Bergmann authored
smbfs has been scheduled for removal in 2.6.27, so maybe we can now move it to drivers/staging on the way out. smbfs still uses the big kernel lock and nobody is going to fix that, so we should be getting rid of it soon. This removes the 32 bit compat mount and ioctl handling code, which is implemented in common fs code, and moves all smbfs related files into drivers/staging/smbfs. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Acked-by:
Jeff Layton <jlayton@redhat.com> Signed-off-by:
-
Greg Kroah-Hartman authored
This lists what's going to happen to the filesystem (i.e. removal in 2.6.38 unless someone steps up to maintain it.) Cc: Arnd Bergmann <arnd@arndb.de> Cc: H. Peter Anvin <hpa@zytor.com> Signed-off-by: -
Arnd Bergmann authored
Nobody appears to be interested in fixing autofs3 bugs any more and it uses the BKL, which is going away. Move this to staging for retirement. Unless someone complains until 2.6.38, we can remove it for good. The include/linux/auto_fs.h header file is still used by autofs4, so it remains in place. Signed-off-by:
H. Peter Anvin <hpa@zytor.com> Signed-off-by:
-
- Oct 05, 2010
-
-
Fernando Guzman Lugo authored
Now the tidspbridge uses the API's from iovmm module. Signed-off-by:
Fernando Guzman Lugo <x0095840@ti.com> Signed-off-by:
-
Ernesto Ramos authored
DSP Bridge needs to disable the peripheral clocks when switches to BRD_STOPPED since that would prevent the domain to enter in OFF state. Signed-off-by:
Ernesto Ramos <ernesto@ti.com> Signed-off-by:
Omar Ramirez Luna <omar.ramirez@ti.com> Signed-off-by:
-
Ernesto Ramos authored
Resendig this patch since it was missed in the last merge... Remove find_lcm within nldr.c and use standard kernel function lcm(). Signed-off-by:
-
Ernesto Ramos authored
Resending this patch since it was missed in the last merge... Remove unnecessary cmm_xlator_delete function and use kfree() kernel function directly. Signed-off-by:
-
Arnd Bergmann authored
This marks up the code where sparse complains in most cases. Most of the changes are in the ioctl handling code, which gets __user annotations, finding one unchecked user access. The rest is mostly about marking functions static when they are only used in one file. Signed-off-by:
-
Arnd Bergmann authored
This removes all warnings I get on a 64 bit build except for those that look unfixable, where we convert a pointer to a 32 bit integer and change its byte order! Signed-off-by:
-
Arnd Bergmann authored
In the original code, address space annotations are missing, which hides a possible unchecked user pointer access. Two functions use a lot of stack space. Extern declarations are all in the wrong place, which leads to type differences between caller and callee in some cases. Signed-off-by:
-
Arnd Bergmann authored
This lets us see clearer when stuff breaks. Most of the changes are fixes for casts between int and pointer that don't work on 64 bit. The ioctl function uses a large amount of stack, which gets fixed by allocating the buffer dynamically. Signed-off-by:
-
Arnd Bergmann authored
unlocked_ioctl has a "long" return type. Signed-off-by:
-
Arnd Bergmann authored
As a preparation for changing the default behaviour of llseek to no_llseek, every file_operations structure should have a .llseek operation. There are three new instances in staging now, which can all be changed into no_llseek explicitly since the devices do not need to seek. Add nonseekable_open where appropriate, to prevent pread/pwrite as well. Signed-off-by:
-
- Oct 02, 2010
-
-
Luis R. Rodriguez authored
Atheros originally had posted a vendor driver to support the Atheros AR9170 devices, the driver was called otus [1]. The otus driver was staging quality but it, along with other chipset documentation helped the community do a rewrite for a proper driver. Johannes Berg did the ar9170 [2] work and Christian Lamparter then followed up with some final touches for inclusion upstream. The original goal behind ar9170 was to match all functionality, performance, stability and quality against Otus. In the end this proved quite challenging even with GPLv2 firmware. Christian then decided to work on a replacement driver with new enhancements to the GPLv2 firmware. It took 1 year, 5 months, 9 days since this merge of ar9170usb upstream to release carl9170 with upstream inclusion intentions but its now there. We remove the Otus driver now as the carl9170 driver actually ends up not only replacing but superseding the staging Otus driver! http://wireless.kernel.org/en/users/Drivers/otus http://wireless.kernel.org/en/users/Drivers/ar9170 http://wireless.kernel.org/en/users/Drivers/carl9170 Signed-off-by:
Luis R. Rodriguez <lrodriguez@atheros.com> Signed-off-by:
-
- Sep 30, 2010
-
-
Maurice Dawson authored
This is a patch to the ni_labpc.c file that fixes up, EXPORT SYMBOL(foo) should immediately follow its function/variable warnings, found by the checkpatch.pl tool Signed-off-by:
Maurice Dawson <mauricedawson2699@gmail.com> Signed-off-by:
-
Brett Rudley authored
wl_remove() is now called from places other than the .remove field of struct pci_driver so do not annotate wl_remove() with __devexit. This removes the debug section mismatch warning introduced by the previous nonexistant firmware patch. Signed-off-by:
Brett Rudley <brudley@broadcom.com> Signed-off-by:
-
Nohee Ko authored
This patch fixes "#ifdef BRCM_FULLMAC" mess which shows in siutils.c/hndpmu.c. All unnecessary #ifdefs were erased. Also as a part of this work, bcmutils.c was also modified. Signed-off-by:
Nohee Ko <noheek@broadcom.com> Signed-off-by:
-
Henry Ptasinski authored
This removes compile flags that are completely unnecessary when building the brcmfmac driver. Also sorts the options to make it a bit easier to look at them. Signed-off-by:
-
Brett Rudley authored
Trim down bcmip.h to only whats needed, purge the rest. Signed-off-by:
-
Brett Rudley authored
Purge unused and extraneous header, brcm80211/include/proto/802.11e.h Signed-off-by:
-
Brett Rudley authored
Delete unused attempt to debug through /proc. Signed-off-by:
-
Brett Rudley authored
Handle non-extistent firmware more gracefully. Signed-off-by:
-
Greg Kroah-Hartman authored
Now that we aren't using the rc_lock variable, delete it to keep gcc happy and not complaining about it. Cc: Al Cho <acho@novell.com> Signed-off-by: -
Al Cho authored
The other part of keucr lost usb disconnect. Unplug SDcard after thread scan,the wrong rule in usb_stor_port_reset, so the driver still fail in stress test. Signed-off-by:
Al Cho <acho@novell.com> Signed-off-by:
-
Arthur Benilov authored
From a95892fc2246d6dc45f57b7dd68f32b9b28bd0f7 Mon Sep 17 00:00:00 2001 From: Arthur Benilov <arthur.benilov@gmail.com> Date: Fri, 24 Sep 2010 13:51:07 +0200 Subject: [PATCH] Staging: vme: Assure D16 cycle if required in master_read and master_write memcpy_fromio() and memcpy_toio() functions apply internally to __memcpy() that performs data transfer in 32-bits or 8-bits blocks (at least on x86). This makes impossible to perform D16 cycle with ca91cx42 bridge. Provided modification assures performing data transfer with 32, 16, and 8 bits chunks. Signed-off-by:
Arthur Benilov <arthur.benilov@iba-group.com> Signed-off-by:
Martyn Welch <martyn.welch@ge.com> Signed-off-by:
-
Phillip Kurtenbach authored
Fixed whitespace coding style issues. Signed-off-by:
Phillip Kurtenbach <pkurtenbach@gmail.com> Acked-by:
Jonathan Cameron <jic23@cam.ac.uk> Signed-off-by:
-
Vasiliy Kulikov authored
Freeing netdev without free_netdev() leads to net, tx leaks. I might lead to dereferencing freed pointer. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/ ) @@ struct net_device* dev; @@ -kfree(dev) +free_netdev(dev) Signed-off-by:
Vasiliy Kulikov <segooon@gmail.com> Acked-by:
Denis Kirjanov <dkirjanov@kernel.org> Signed-off-by:
-
Vasiliy Kulikov authored
It is not guaranteed that free_netdev() is macro. Freeing netdev without free_netdev() leads to net, tx leaks. I might lead to dereferencing freed pointer. Signed-off-by:
David Daney <ddaney@caviumnetworks.com> Signed-off-by:
-
Vasiliy Kulikov authored
It is not guaranteed that free_netdev() is macro. Freeing netdev without free_netdev() leads to net, tx leaks. I might lead to dereferencing freed pointer. Signed-off-by:
-
