- 26 Aug, 2002 12 commits
-
-
bk://ldm.bkbits.net/linux-2.5-clsLinus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Benjamin LaHaise authored
For some reason, quota.h was derrived from BSD 4 clause code. Thankfully, UCB gave permission to remove the advert clause a couple of years ago, so it's now okay for us to actually distribute this code. The following patch updates the header in quota.h.
-
Chuck Lever authored
this eliminates an infinite loop in rpciod if an RPC client's reference counter accidentally goes negative. i've been running this under load since 2.5.30 with no ill effects.
-
Kai Mäkisara authored
This adds direct write and read from/to the user space to/from the SCSI adapter. If something (e.g., too high address) prevents direct transfer, the existing driver buffer code is used. The patch contains functions to map and pin the user buffer pages so that this patch is not dependent on kiobufs. Similar functions are already used in sg.c.
-
Linus Torvalds authored
-
bk://jfs.bkbits.net/linux-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Jan-Benedict Glaw authored
Please import this patch. It updates the Config.help entry (which some people requested) and cleans up coding a bit. No functional changes.
-
Luca Barbieri authored
GCC can only inline functions when the function definition comes before its use.
-
Vojtech Pavlik authored
-
Vojtech Pavlik authored
Recompute keybit when keycode table changes. Stricter checks on input keycode/scancode values.
-
Patrick Mochel authored
Device interfaces are the logical interfaces of device classes that correlate directly to userspace interfaces, like device nodes. Device interfaces are registered with the class they belong to. As devices are added to the class, they are added to each interface registered with the class. The interface is responsible for determining whether the device supports the interface or not. The interface is responsible for allocating and initializing a struct intf_data and calling interface_add_data() to add it to the device's list of interfaces it belongs to. This list will be iterated over when the device is removed from the class (instead of all possible interfaces for a class). This structure should probably be embedded in whatever per-device data structure the interface is allocating anyway. Devices are enumerated within the interface. This happens in interface_add_data() and the enumerated value is stored in the struct intf_data for that device. Interfaces get a directory in driverfs under their class's directory. Each time a device is added to the interface, a symlink is created in that directory that points to the device's directory in the physical hierarchy. The name of this symlink is the interface-enumerated value of the device.
-
Patrick Mochel authored
Device classes describe a type (or class) of device, like an input device or network device, etc. This changeset defines a struct device_class that each subsystem is expected to implement and register with the core. struct device_driver gains a devclass pointer which points to the class it belongs to. When the driver is registered, it is added to the class's list of drivers. Whenever a device is bound to that driver, it is added to the class by calling the class's add_device callback. struct device gains a class_num field which is the per-class enumerated value of the device. It is incremented each time a device is registered with the class. Each device class gets a driverfs directory in class/<class name> and two subdirectories: 'devices' and 'drivers'. For each device added to the class, a symlink is created in the devices/ directory that points to the device's directory in the physical hierarchy. The name of the symlink is the enumerated number the device got when it was registered with the class. For each driver that's added to the class, a symlink is created in the class's drivers/ directory that points to the driver's directory. The name of this symlink is a concatenation of <bus name>:<driver name> (to prevent namespace conflicts of drivers with the same name on different buses).
-
- 25 Aug, 2002 17 commits
-
-
Vojtech Pavlik authored
-
Vojtech Pavlik authored
as functions interfacing to the input core. PC-Speaker handling is moved to a separate file. Uinput is moved to a input/misc directory.
-
http://linuxusb.bkbits.net/linus-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Kai Germaschewski authored
into zephyr.physics.uiowa.edu:/home/kai/src/kernel/v2.5/linux-2.5.make
-
Kai Germaschewski authored
Greg Banks: A very significant space is missing from an "if" expression in drivers/video/Config.in.
-
Kai Germaschewski authored
Greg Banks: Symbols CONFIG_BLK_DEV_NS87415, CONFIG_BLK_DEV_TRM290, CONFIG_DSCC4, and CONFIG_USB_SERIAL_SAFE_PADDED had spurious (EXPERIMENTAL) tags in their banners. Symbol CONFIG_INPUT_UINPUT was missing an (EXPERIMENTAL) tag in it banner.
-
Kai Germaschewski authored
The mips and parisc ports both defined 'Loadable module support' menus, despite including an identical menu from init/Config.in.
-
Kai Germaschewski authored
Greg Banks: The symbol CONFIG_SOUND_CMPCI_FMIO is declared with a "hex" statement, immediately preceded by a "define_hex" with the same value as the default value from the "hex". In config and xconfig, this has no effect; in menuconfig it prevents the user selecting any value other than the default.
-
Kai Germaschewski authored
Greg Banks: The symbol CONFIG_DEBUG_SPINLOCK was defined twice identically in the same file...three lines apart.
-
Kai Germaschewski authored
Greg Banks: A number of dep_bools and dep_tristates have architecture constants (e.g. CONFIG_X86) as dependencies. Such symbols have the property that their value is constant for any particular arch tree, and is either "y" or "", neither of which have any effect as dependencies, so the dependencies have no effect. This patch removes some of them.
-
Kai Germaschewski authored
Greg Banks: The menu 'AX.25 network device drivers' contained as its first item a comment with identical banner. This is pointless duplication, but more to the point it confused gcml2 unnecessarily.
-
Kai Germaschewski authored
-
Linus Torvalds authored
-
Linus Torvalds authored
Cset exclude: torvalds@home.transmeta.com|ChangeSet|20020821235957|57282
-
Ingo Molnar authored
This patch simply ensures that 'setting the MTRR' is atomic. This is important since HT CPU's may share some MTRR state.
-
- 23 Aug, 2002 11 commits
-
-
David S. Miller authored
- Do not use PC-relative branch/call in Ultra-III+ parity error trap vectors, we patch this into the trap table and then the PC-relative values are wrong. - When we take an irrecoverable trap at tl > 0, save away the full trap stack to the kernel stack, then log it from the C code handler.
-
David S. Miller authored
-
David S. Miller authored
- Some places need to include sched.h because the already include ptrace.h - CLONE_{SET,CLEAR}TID support - Clear PT_DTRACE when execve succeeds. - Add security bits to ptrace - Add sys_security to syscall tables.
-
David S. Miller authored
- Some places need to include sched.h because the already include ptrace.h - CLONE_{SET,CLEAR}TID support - Clear PT_DTRACE when execve succeeds. - Add security bits to ptrace and sys32_execve - Add sys_security to syscall tables.
-
David S. Miller authored
- futex uses int as its atomic word type, we pass in user_tid to the futex routines, so the types must match
-
David S. Miller authored
- flush_dcpage_cheetah sized wrongly, it is 11 not 9 insns now - xcall_report_regs and xcall_promstop should use etrap_irq not etrap
-
Christoph Hellwig authored
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/sparc-2.5
-
David S. Miller authored
-
David S. Miller authored
-