- 26 May, 2003 40 commits
-
-
Shmulik Hen authored
This patch fixes the bug reported by Jay on April 3rd regarding long failover time when releasing the last slave in the active aggregator. The fix, as suggested by Jay, is to follow the spec recommendation and send a LACPDU to the partner saying this port is no longer aggregatable and therefore trigger an immediate re-selection of a new aggregator instead of waiting the entire expiration timeout.
-
Ben Collins authored
- Adds fragementation support to eth1394 - Fix race conditition in packet completion task call - Fix lack of proper logic in tlabel allocation - Fix brokeness introduced by "stanford checker fixes for memset" in ohci1394 - Add trivial PM resume callback in ohci1394 to support sleep/resume.
-
bk://linux-scsi.bkbits.net/scsi-for-linus-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
James Bottomley authored
into raven.il.steeleye.com:/home/jejb/BK/scsi-for-linus-2.5
-
James Bottomley authored
into raven.il.steeleye.com:/home/jejb/BK/scsi-for-linus-2.5
-
James Bottomley authored
-
James Bottomley authored
-
James Bottomley authored
The data direction for the SCSI command was being strangely deduced by checking for an old WRITE_6 command.
-
James Bottomley authored
This makes the driver compile and run on the PARISC platform. The biggest issue for this driver is the firmware layout because the chip insists on reading from firmware a 16 bit word at a time, so the entire byte layout of the firmware had to be reversed.
-
Andrew Morton authored
This patch will put us back to the 2.4 behaviour while preserving the truncation speedup. It's a bit dopey (why do the timestamp update in the fs at all?) but changing this stuff tends to cause subtle problems.
-
ssh://linux-scsi@linux-scsi.bkbits.net/scsi-misc-2.5James Bottomley authored
into raven.il.steeleye.com:/home/jejb/BK/scsi-misc-2.5
-
James Bottomley authored
-
James Bottomley authored
-
Linus Torvalds authored
-
Rusty Russell authored
From: Hanna Linder <hannal@us.ibm.com>
-
Rusty Russell authored
From: René Scharfe <l.s.r@web.de> this fixes a trivial error in isofs/inode.c, and reformats the surrounding code a bit to (hopefully) enhance clarity. i_mtime.tv_nsec was initialized twice, and i_ctime.tv_nsec never
-
Rusty Russell authored
From: Rusty Russell <rusty@rustcorp.com.au> Trivial unused var...
-
Rusty Russell authored
From: René Scharfe <l.s.r@web.de> This un-complicates a small piece of code of the dev/pts filesystem and decreases the size of the object code by 8 bytes for my build. Yay! :)
-
Rusty Russell authored
From: Tom Rini <trini@kernel.crashing.org> The following marks videodev_proc_destory as __exit. This is safe as its only caller is marked as __exit as well.
-
Rusty Russell authored
From: Pavel Machek <pavel@ucw.cz> This kills a compile warning in swsusp
-
Rusty Russell authored
From: Stephen Rothwell <sfr@canb.auug.org.au> This allows some architecture to override the generic implementations on {get,put}_compat_flock64 as some of them (ia64 and maybe x86_64) will take alignment faults when accessing the loff_t members of struct compat_flock64. Requested by David Mosberger, modified by Dave Miller.
-
Rusty Russell authored
From: Pavel Machek <pavel@ucw.cz>
-
Rusty Russell authored
From: Pavel Machek <pavel@ucw.cz> This adds some more commentary to the boot-up code.
-
Rusty Russell authored
From: Scott Russell <scott@pantastik.com> - missing release_region (reported by kbugs.org) - removed extraneous return (Randy Dunlap)
-
Rusty Russell authored
From: Pavel Machek <pavel@ucw.cz> This fixes url in ioctls, fixes some kernel parameters, kills comment in tty that is 10+ years old and wrong, and adds me a little credits.
-
Rusty Russell authored
From: Jonathan Corbet <corbet@lwn.net> This fixes a couple of little mistakes in Documentation/NAPI_HOWTO.txt; I also updated the interrupt handler stuff while I was at it. Jamal Hadi Salim has seen and acked it.
-
Rusty Russell authored
From: Scott Russell <scott@pantastik.com> - Rearranged unreachable code reported via kbugs.org
-
Rusty Russell authored
From: Matthew Wilcox <willy@debian.org> These defines are simply not used any more.
-
Rusty Russell authored
From: Jesse Barnes <jbarnes@sgi.com> Quick add to the maintainers file for SN (aka Altix 3000) support in the kernel.
-
Rusty Russell authored
From: Adrian Bunk <bunk@fs.tum.de> the patch below removes the unneeded #define LinuxVersionCode from eata.c. It's not used and if it was needed KERNEL_VERSION in include/linux/version.h does the same.
-
Rusty Russell authored
From: Steven Cole <elenstev@mesatop.com> This is a slightly improved version of the additional help texts for sound/oss/Kconfig. The originals were obtained from 2.4.21-pre4.
-
Rusty Russell authored
From: Scott Russell <scott@pantastik.com> - Rearranged unreachable code reported at kbugs.org
-
Rusty Russell authored
From: Adrian Bunk <bunk@fs.tum.de> The following trivial patch updates the short description for BLK_DEV_HPT366 (the HPT372 and the HPT374 are supported, too):
-
Rusty Russell authored
From: Jonathan Corbet <corbet@lwn.net> This fix has been acked by James Bottomley, but has not risen above Linus's threshold.
-
Rusty Russell authored
From: Rusty Russell <rusty@rustcorp.com.au> I don't think it's misused anywhere, but it's better to be safe. Pointed out by Joern Engel.
-
Rusty Russell authored
From: Scott Russell <scott@pantastik.com> - moved return to eliminate unreachable code reported by kbugs.org
-
Rusty Russell authored
From: Amit Shah <shahamit@gmx.net> The read function for consoles in include/linux/console.h contains const char* for a pointer that it will actually modify. Although no one seems to be using this as of now, it should be corrected.
-
Greg Ungerer authored
No longer need to call the 68328 specific int setup. Now all done by the common 68328 int handler code.
-
Greg Ungerer authored
No longer need to call the hardware specific int setup. This is now done in the common int handler for 68328 sub-architecture.
-
Greg Ungerer authored
Modify the m68knommu/68328 specific ints.c to be the general ints handler when building for this sub-architecture. It is just simpler to have one for each sub-architecture (which means we currently need 3 for the 3 prominant m68knommu families). Each can handle the hardware setup differences, and there is a few at this level. This doesn't really add much code overall, since 2 of the 3 m68knommu architectures already had significant specific int handling code.
-