- 29 Oct, 2004 3 commits
-
-
Andrew Morton authored
The data structures which are set up by key_init() are used by exec(). And we're using exec() super-early via the hotplug events from do_basic_setup():driver_init(). So call key_init() directly, prior to driver_init(). Cc: David S. Miller <davem@davemloft.net> Cc: David Howells <dhowells@redhat.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Pavel Machek authored
This adds typechecking to suspend types and powerdown types. This should solve at least part of suspend type confusion. There should be no code changes generated by this one. Acked-by:
Patrick Mochel <mochel@digitalimplant.org> Signed-off-by:
-
Toshihiro Iwamoto authored
It seems that O_DIRECT write sometimes leaks memory. Signed-off-by:
-
- 28 Oct, 2004 37 commits
-
-
Andi Kleen authored
The x86-64 genapic patch that was recently merged missed some definitions and doesn't compile at all. This fixes it by adding the missing defines for genapic Signed-off-by:
Andi Kleen <ak@muc.de> Signed-off-by:
-
Tom Rini authored
D'oh. Something got cut-off there on Randy's end. Obviously correct fix follows. Signed-off-by:
Tom Rini <trini@kernel.crashing.org> Signed-off-by:
-
Olaf Hering authored
this sequence of commands will hang the final rmmod. init=/bin/bash --login mount proc modprove -v ohci1394 rmmod ohci1394 modprobe -v ohci1394 rmmod ohci1394 -> hangs knodemgrd_0 exits on the first rmmod, but leaves nodemgr_serialize in down state. This fixes it for me. Signed-off-by:
Olaf Hering <olh@suse.de> Acked-by:
Ben Collins <bcollins@debian.org> Signed-off-by:
-
http://lia64.bkbits.net/linux-ia64-release-2.6.10Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Stephen Rothwell authored
This merges two files (iSeries_IoMmTable.[ch]) into iSeries_pci.c. This allowed quite a few more things to become declared static. It then does some fairly mechanical cleanups in iSeries_pci.c (replacing studly caps, removing the last of the PCIFR() macros and removing a couple of empty or unused routines). There are no semantic changes. Signed-off-by:
Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by:
-
Martin Wilck authored
The "Synchronize Arbitration IDs with APIC IDs" IPI does not make sense on Pentium 4 and Xeon because they don't have an APIC bus where arbitration IDs would be needed. The Intel Developers manual (Vol. 3, Ch. 8.6.1) says this IPI is unsupported on P4/Xeon. Using it may, according to Intel, lead to unpredictable results. Signed-off-by:
Martin Wilck <martin.wilck@fujitsu-siemens.com> Signed-off-by:
-
Stelian Pop authored
Signed-off-by:
Stelian Pop <stelian@popies.net> Signed-off-by:
-
Stelian Pop authored
Signed-off-by:
-
Stelian Pop authored
Leave the choice to the user. Signed-off-by:
-
Stelian Pop authored
Signed-off-by:
-
Stelian Pop authored
* feed most of special keys through the input subsystem * initialize two separate input devices: a mouse like one for the jogdial and a keyboard like one for the special keys * add support for SONYPI_EVENT_FNKEY_RELEASED Many people participated in a way or another to this patch, including Daniel K. <daniel@cluded.net>, Bastien Nocera <hadess@hadess.net>, Dmitry Torokhov <dtor@mail.ru> and Vojtech Pavlik <vojtech@suse.cz>. Signed-off-by:
-
Stelian Pop authored
* switch from a sysdev to a platform device * drop old style PM code * use pci_get_device()/pci_dev_put() instead of pci_find_device() Patch originaly from Dmitry Torokhov <dtor@mail.ru>. Signed-off-by:
-
Stelian Pop authored
Signed-off-by:
-
Stelian Pop authored
* use module_param() instead of MODULE_PARM() and __setup() * use MODULE_VERSION() Signed-off-by:
-
Chris Wright authored
Early calls to userspace can invoke an execve() before any binfmt handlers are registered. Properly return an error in this case rather than 0. On at least one arch (x86_64) without this patch, the system will double fault on early attempts to call_usermodehelper. Signed-off-by:
Chris Wright <chrisw@osdl.org> Signed-off-by:
-
Chris Wedgwood authored
Remove build warning from drivers/char/random.c on 32-bit platforms. Signed-off-by:
Chris Wedgwood <cw@f00f.org> Signed-off-by:
-
Olaf Hering authored
__handle_sysrq already prints a newline, so the action_msg string doesnt need yet another newline. Signed-off-by:
-
Gerd Knorr authored
- Make bttv check the device_register return value. - Yet another unchecked return value fixed. Signed-off-by:
Gerd Knorr <kraxel@bytesex.org> Signed-off-by:
-
Jens Axboe authored
There are two issues with online io scheduler switching that this patch addresses. The first is pretty simple - it concerns racing with scheduler removal on switch. elevator_find() does not grab a reference to the io scheduler, so before elevator_attach() is run it could go away. Add elevator_get() to solve that. Second issue is the flushing out of requests that is needed before switching can be problematic with requests that aren't allocated in the block layer (such as requests on the stack of a process). The problem is that we don't know when they will have finished, and most io schedulers need to access the elevator structures on io completion. This can be fixed by adding an intermedia step that switches to noop, since it doesn't need to touch anything but the request_queue. The queue drain can then safely be split into two operations - one that waits for file system requests, and one that waits for the queue to completely empty. Requests arriving after the first drain will get stuck in a seperate queue list. Signed-off-by:
Jens Axboe <axboe@suse.de> Signed-off-by:
-
Manfred Spraul authored
register_sysctl_table() fails if sysctl support is not compiled into the kernel. The POSIX message queue subsystem aborted it's initialization if register_sysctl_table() fails, and that causes an oops in sys_mq_open(). The patch fixes that by ignoring failures from register_sysctl_table(). Signed-off-by; Manfred Spraul <manfred@colorfullife.com> Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Jens Axboe authored
Fix online switching issue with cfq v2. It does deferred clearing of e->elevator_data, which screws up the current io scheduler. It does not have to, so just remove it. Signed-off-by:
-
William Lee Irwin III authored
These two variables are long, long dead. This patch removes them. Signed-off-by:
William Irwin <wli@holomorphy.com> Signed-off-by:
-
Colin Leroy authored
This patch fixes via-pmu.c compilation when CONFIG_PMAC_PBOOK is not set. Looks like the #endif was one line too late. Signed-off-by:
Colin Leroy <colin@colino.net> Acked-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Christoph Hellwig authored
It's been totally obsoleted by the input layer Acked-by:
Alan Cox <alan@redhat.com> Signed-off-by:
-
Christoph Hellwig authored
This was used by the early irqstacks implementation on s390 and has been replaced by __ARCH_HAS_DO_SOFTIRQ now. Signed-off-by:
-
Christoph Hellwig authored
module_attribute.show is defined to return ssize_t Signed-off-by:
-
Thomas Gleixner authored
To make spinlock/rwlock initialization consistent all over the kernel, this patch converts explicit lock-initializers into spin_lock_init() and rwlock_init() calls. Currently, spinlocks and rwlocks are initialized in two different ways: lock = SPIN_LOCK_UNLOCKED spin_lock_init(&lock) rwlock = RW_LOCK_UNLOCKED rwlock_init(&rwlock) this patch converts all explicit lock initializations to spin_lock_init() or rwlock_init(). (Besides consistency this also helps automatic lock validators and debugging code.) The conversion was done with a script, it was verified manually and it was reviewed, compiled and tested as far as possible on x86, ARM, PPC. There is no runtime overhead or actual code change resulting out of this patch, because spin_lock_init() and rwlock_init() are macros and are thus equivalent to the explicit initialization method. Signed-off-by:
Thomas Gleixner <tglx@linutronix.de> Acked-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Thomas Gleixner authored
To make spinlock/rwlock initialization consistent all over the kernel, this patch converts explicit lock-initializers into spin_lock_init() and rwlock_init() calls. Currently, spinlocks and rwlocks are initialized in two different ways: lock = SPIN_LOCK_UNLOCKED spin_lock_init(&lock) rwlock = RW_LOCK_UNLOCKED rwlock_init(&rwlock) this patch converts all explicit lock initializations to spin_lock_init() or rwlock_init(). (Besides consistency this also helps automatic lock validators and debugging code.) The conversion was done with a script, it was verified manually and it was reviewed, compiled and tested as far as possible on x86, ARM, PPC. There is no runtime overhead or actual code change resulting out of this patch, because spin_lock_init() and rwlock_init() are macros and are thus equivalent to the explicit initialization method. Signed-off-by:
-
Pawel Sikora authored
Signed-off-by:
-
James Nelson authored
Description: Cleanup and update to Documentation/ftape.txt Signed-off by: James Nelson <james4765@gmail.com> Signed-off-by:
-
James Nelson authored
After tracking down the original author of the ftape sources, I found out that he no longer had interest in maintaining it. Signed-off-by:
James Nelson <james4765@gmail.com> Signed-off-by:
-
Werner Almesberger authored
Allow the buffer_foo() predicates to take a (const struct buffer_head *). I've checked that the argument of test_bit is indeed "const" on all architectures. Signed-off-by:
Werner Almesberger <werner@almesberger.net> Signed-off-by:
-
Jesper Juhl authored
Add a bunch of entries to Documentation/00-INDEX that are currently missing (and removes the entry for one file that no longer exist). Patch has already been OK'ed by Paul G. Signed-off-by:
Jesper Juhl <juhl-lkml@dif.dk> Signed-off-by:
-
Peter Osterlund authored
cdrom_is_mrw() can incorrectly think that a drive is Mt Rainier capable, because if forgets to check if the "GET CONFIGURATION" command returns the MRW feature number. According to the MMC spec, the drive shall return all feature numbers >= the starting feature number, so even if the drive doesn't support Mt Rainier, it can return some data that makes cdrom_is_mrw() incorrectly think the drive is MRW capable. This problem stops me from mounting DVD+RW discs in R/W mode on my laptop, because it makes cdrom_open_write() call cdrom_mrw_open_write() which fails because the drive isn't really MRW capable. The fix is to make sure the returned feature number is the correct one for Mt Rainier. Signed-off-by:
Peter Osterlund <petero2@telia.com> Acked-by:
-
Arjan van de Ven authored
add_timer_on() isn't used by modules (in fact it's only used ONCE, in workqueue.c) and it's not even a good api for drivers, in fact, the comment for it says * This is not very scalable on SMP. Double adds are not possible. Signed-off-by:
Arjan van de Ven <arjan@infradead.org> Acked-by:
-
Jens Axboe authored
Don't know where this came from, but dumping this on every open gets boring really quickly. Signed-off-by:
-
David Howells authored
Remove some of the exports on RxRPC symbols that aren't currently used (and most probably won't be) by external modules. Signed-off-by:
David Howells <dhowells@redhat.com> Signed-off-by:
-
