- 15 Nov, 2004 4 commits
-
-
Phil Oester authored
Signed-off-by:
Phil Oester <kernel@linuxace.com> Signed-off-by:
Patrick McHardy <kaber@trash.net>
-
Patrick McHardy authored
into coreworks.de:/home/kaber/src/nf/nf-2.6
-
Patrick McHardy authored
into coreworks.de:/home/kaber/src/nf/nf-2.6
-
Patrick McHardy authored
into coreworks.de:/home/kaber/src/nf/nf-2.6
-
- 13 Nov, 2004 7 commits
-
-
Patrick McHardy authored
Signed-off-by: -
Patrick McHardy authored
Signed-off-by: -
Adrian Bunk authored
Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
David S. Miller authored
This fixes up ChangeSet 1.2086.1.75 Signed-off-by: -
Patrick McHardy authored
Signed-off-by: -
Patrick McHardy authored
Signed-off-by: -
Patrick McHardy authored
Signed-off-by:
-
- 11 Nov, 2004 29 commits
-
-
bk://bk.skbuff.net:20610/linux-2.6-inet6-misc/David S. Miller authored
into nuts.davemloft.net:/disk1/BK/net-2.6
-
Patrick McHardy authored
This patch fixes on overflow in tc actions times reported to userspace on 64 bit architectures. struct tcf_t only contains 32-bit timestamps, but they are initialized to jiffies. When jiffies is larger than 2^32-1 only the low 32 bit are saved, and the diff between jiffies and the current timestamp becomes very large. This happens immediately after boottime since jiffies is initialized to 2^32-300. It was invisible until now because only the lower 32bit were reported to userspace, but with the USER_HZ conversion the reported times start somewhere around 4294967s. This patch extends the timestamps to 64bit. It breaks userspace compatibility for actions, but considering that most of this is not even in iproute yet this should be acceptable. Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by: -
Andrew Morton authored
Limit the number of legacy ptys to 256. pty_line_name() isn't capable of generating more than 256 unique names. Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Arjan van de Ven authored
task_nice() was exported for binfmt_elf, however that's no longer modular. normalize_rt_tasks() is used by the sysreq code only, which isn't modular. Signed-off-by:
Arjan van de Ven <arjan@infradead.org> Signed-off-by:
-
Arjan van de Ven authored
- cdev_get is only used in fs/char_dev.c; move it up, make it static and unexport it. - cdev_put is used in one more place (fs/file_table.c) but never in modules; unexport it. Signed-off-by:
-
Domen Puncer authored
Code looks like it intended to parse "%%" in pattern string as "%". Fix it, so it really does that. Compile and run tested. Signed-off-by:
Domen Puncer <domen@coderock.org> Signed-off-by:
-
Randy Dunlap authored
Convert MODULE_PARM() to module_param(). Signed-off-by:
Randy Dunlap <rddunlap@osdl.org> Signed-off-by:
-
Randy Dunlap authored
Convert MODULE_PARM() to module_param(). Signed-off-by:
-
James Nelson authored
Updates to Documentation/md.txt - included some extra info I found out while digging deeper into init/do_mounts_md.c Signed-off-by:
James Nelson <James4765@gmail.com> Signed-off-by:
-
Neil Brown authored
The 'faulty' personality provides a layer over any block device in which errors may be synthesised. A variety of errors are possible including transient and persistent read and write errors, and read errors that persist until the next write. There error mode can be changed on a live array. Accessing this personality requires mdadm 2.8.0 or later. Signed-off-by:
Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
-
Neil Brown authored
As the unplug timer can potentially fire at any time, and and it access data that is released by the md ->stop function, we need to del_timer_sync before releasing that data. (After much discussion, we created blk_sync_queue() for this) Signed-off-by:
-
Neil Brown authored
Sometimes it didn't read all (working) drives before a parity calculation. Signed-off-by:
-
Neil Brown authored
Some size fields were "int" instead of "sector_t". Signed-off-by:
-
Antonino Daplas authored
This patch fixes some of the drivers' fb_blank() implementation which got the usage of the VESA_* constants incorrectly and converts them to use the new FB_BLANK-* constants. I'm not sure if what I did is correct for all drivers, so maintainers, please review. (Note: For most of the drivers, FB_BLANK_NORMAL is treated as FB_BLANK_UNBLANK, but returns a nonzero so fbcon will do a soft_blank). Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
This patch converts most drivers to use the new FB_BLANK_* constants. These drivers have correct fb_blank() implementations. Signed-off-by:
-
Antonino Daplas authored
The VESA_* constants in fb.h used for power management of the display is confusing to use. The constants seems to be meant for userspace, because within the kernel (vt and fbdev), the constants have to be incremented by 1. Implementation of fb_blank() varies from driver to driver: - if-else on blank/!blank - switch case on hardcoded numbers - switch case on the constants + 1 - switch -1, case on constants as is - switch case on the constants as is (broken) To make usage clearer, new constants are defined in fb.h: FB_BLANK_UNBLANK = VESA_UNBLANKING = 0; FB_BLANK_NORMAL = VESA_UNBLANKING + 1 = 1; FB_BLANK_VSYNC_SUSPEND = VESA_VSYNC_SUSPEND + 1 = 2; FB_BLANK_HSYNC_SUSPEND = VESA_HSYNC_SUSPEND + 1 = 3; FB_BLANK_POWERDOWN = VESA_POWERDOWN + 1 = 4; Other changes: - generic blanking code in fbcon.c (for drivers without an fb_blank hook) which either sets the palette to all black, or clear the screen with black. - make fb_display an unexportable symbol Signed-off-by:
-
Antonino Daplas authored
The function set_con2fb_map() is getting very big. Split it into its component functions. Signed-off-by:
-
Antonino Daplas authored
Set color depth to 8 if in pseudocolor in vesafb. The CLUT size, previously saved as {red|green|blue}.length, is now private to vesafb. Signed-off-by: -
Antonino Daplas authored
The hardware cursor implementation in i810fb broke sometime during 2.6. Until this is fixed, temporarily use soft_cursor(). Signed-off-by:
-
Antonino Daplas authored
The current code in rivafb will not accept modes other than 640x480-60 if the the EDID block is absent. This patch changes the behavior to the opposite, if without an EDID, rivafb will accept all modelines coming from userspace (2.4 behavior). Signed-off-by:
-
Antonino Daplas authored
Convert direct pointer manipulation to NV_RD*/NV_WR* in nv_driver.c Signed-off-by:
-
Jens Axboe authored
The direct-io code currently returns -EIO if someone tries to read past the end of a block device. Change it to shorten the read and to return the number of bytes which were actually read. Signed-off-by:
Jens Axboe <axboe@suse.de> Signed-off-by:
-
Gerd Knorr authored
The patch below removes an unused function from media/video/bw-qcam.c Signed-off-by:
Gerd Knorr <kraxel@bytesex.org> Signed-off-by:
-
Gerd Knorr authored
Fix for the msp3400 module: make the initial carrier scan (after loading the driver) work. Signed-off-by:
-
Gerd Knorr authored
Convert v4l1-compat module to new-style insmod options. Signed-off-by:
-
Gerd Knorr authored
Convert the ir-common module to new-style insmod options. Signed-off-by:
-
Gerd Knorr authored
Convert leftover insmod options to new-style. Signed-off-by:
-
Gerd Knorr authored
Adapt saa7134 driver to video-buf changes. Signed-off-by:
-
