An error occurred fetching the project authors.
- 10 Feb, 2003 27 commits
-
-
Andrew Morton authored
Patch from William Lee Irwin III <wli@holomorphy.com> Don't touch IO-APIC physid's on NUMA-Q. The BIOS pre-programs them.
-
Andrew Morton authored
Patch from Ravikiran G Thirumalai <kiran@in.ibm.com> Converts the ia32 kernel profiler to use use the percpu area infrastructure.
-
Andrew Morton authored
uninline get_jiffies_64() for 32-bit architectures
-
Randy Dunlap authored
Part of the bounds checking bugs found by the Stanford checker. The 4 fixes below have been acked by their maintainers.
-
Andrew Morton authored
Move the definition of version[] down to where __initdata has been defined.
-
Andrew Morton authored
Patch from Joel Becker <Joel.Becker@oracle.com> The task_struct->sig -> task_struct->signal bits.
-
Andrew Morton authored
Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz> points out a bug in ll_rw_block() usage. Typical usage is: mark_buffer_dirty(bh); ll_rw_block(WRITE, 1, &bh); wait_on_buffer(bh); the problem is that if the buffer was locked on entry to this code sequence (due to in-progress I/O), ll_rw_block() will not wait, and start new I/O. So this code will wait on the _old_ I/O, and will then continue execution, leaving the buffer dirty. It turns out that all callers were only writing one buffer, and they were all waiting on that writeout. So I added a new sync_dirty_buffer() function: void sync_dirty_buffer(struct buffer_head *bh) { lock_buffer(bh); if (test_clear_buffer_dirty(bh)) { get_bh(bh); bh->b_end_io = end_buffer_io_sync; submit_bh(WRITE, bh); } else { unlock_buffer(bh); } } which allowed a fair amount of code to be removed, while adding the desired data-integrity guarantees. UFS has its own wrappers around ll_rw_block() which got in the way, so this operation was open-coded in that case.
-
Dave Jones authored
into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart-respin
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
This removes lots of annoying problems trying to prevent both modules from being loaded, and also shares quite a bit of code. CONFIG_AGP3 will disable AGP3 mode operation of KT400s.
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
Based upon information from VIA, this also adds a bunch of placeholder entries that will get filled in over time when they have been proven to work with the code with no extra modification.
-
Dave Jones authored
The AGP3 spec allows for >1 AGP bus. This is the first of several patches from Jeff Hartmann towards a context-using agp_bridge, by replacing agp_bridge.foo accesses with agp_bridge->foo accesses. For now, there should be no functional differences, as there is still only a single agp_bridge_data struct defined.
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
-
Linus Torvalds authored
-
Steven Cole authored
Most of the instances of <module>.o in Kconfig files have had the ".o" extension trimmed. This change came from GertJan Spoelman through Rusty "Trivial" Russell. However, there are a few files that didn't get trimmed. This brings them line with the rest of the tree.
-
- 09 Feb, 2003 13 commits
-
-
Linus Torvalds authored
so that there isn't any window for running before the signal handler has been invoced.
-
Linus Torvalds authored
from certain states. This simplifies "default_wake_function()", and makes it possible for signal handling to wake up only the processes it _should_ wake up without races.
-
Rusty Russell authored
From: GertJan Spoelman <kl@gjs.cc> OK, here is a new patch, I edited the old patch and took out the .ko's so now the extension is trimmed instead.
-
Rusty Russell authored
[ Acked by AKPM --RR ] From: Kazuto MIYOSHI <miyoshi@hpc.bs1.fc.nec.co.jp> On 64-bit platforms, issuing write(2) with buffer larger than 2GB will return -1 and broken errno (such as 2147483640) Requested data itself is written correctly. That is because generic_file_write() and other relating functions store 'ssize_t written' into 'int err'. Written byte is trimmed to int and then sign-extended to a negative ssize_t value, which wrongly indicates an error. (On 64bit platform, current glibc defines SSIZE_MAX as 'LONG_MAX')
-
Rusty Russell authored
From: Steven Cole <elenstev@mesatop.com> Here are some help texts from 2.4.21-pre3 Configure.help which are needed in 2.5.59 drivers/media/video/Kconfig.
-
Rusty Russell authored
From: Pablo Menichini <pablo@menichini.com.ar>
-
Rusty Russell authored
From: Steven Cole <elenstev@mesatop.com> Here are some help texts from 2.4.21-pre3 Configure.help which are needed in 2.5.59 drivers/char/watchdog/Kconfig.
-
Rusty Russell authored
From: Steven Cole <elenstev@mesatop.com> Here are some help texts from 2.4.21-pre3 Configure.help which are needed in 2.5.59 drivers/ide/Kconfig.
-
Rusty Russell authored
From: Pavel Machek <pavel@ucw.cz> This patch makes kernel ignore bad signature on suspend device when "noresume" is given, and cleans things up a little bit. Please apply,
-
Rusty Russell authored
[ Verified that no text changed with tr and cmp --RR ] From: ookhoi@humilis.net With this patch I tried to make Documentation/arm/SA1100/CERF more readible by fixing the linewrap.
-
Rusty Russell authored
From: Steven Cole <elenstev@mesatop.com> This fixes the only instance of "kernal" in 2.5.59.
-
Rusty Russell authored
From: David Gibson <david@gibson.dropbear.id.au> is never used, so this patch removes it.
-
Rusty Russell authored
From: William Lee Irwin III <wli@holomorphy.com> This trivially corrects an unused variable warning in nfs/write.c:
-