- 01 Oct, 2006 40 commits
-
-
Thomas Petazzoni authored
Prevent multiple inclusions of include/linux/sysrq.h using traditional #ifndef..#endif. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@enix.org> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Pierre Ossman authored
Clarify my (Pierre's) position on which GPL versions apply. The patch only touches the source files where I am the only major author. The people who have made the minor commits to the files have been contacted and have no issues with this change. Signed-off-by:
Pierre Ossman <drzeus@drzeus.cx> Cc: Russell King <rmk@arm.linux.org.uk> Signed-off-by:
-
Olaf Hering authored
Remove unused global SYSRQ_KEY from ppc and powerpc Remove unused define SYSRQ_KEY from sh/sh64 and h8300 Remove unused pckbd_sysrq_xlate and kbd_sysrq_xlate usage Signed-off-by:
Olaf Hering <olaf@aepfle.de> Cc: Paul Mundt <lethal@linux-sh.org> Cc: Kazumoto Kojima <kkojima@rr.iij4u.or.jp> Cc: Paul Mackerras <paulus@samba.org> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Jiri Slaby authored
- loading of firmware didn't fail when something went wrong (returned 0). - pointer to frame was incremented only by sizeof(frame) excluding its data contents -- bad idea. - tell the card we're ready just after checking is complete, not before. Signed-off-by:
Jiri Slaby <jirislaby@gmail.com> Signed-off-by:
-
Diego Calleja authored
Signed-off-by:
Diego Calleja <diegocg@gmail.com> Signed-off-by:
-
Rolf Eike Beer authored
If cdev_add() fails there is no good reason to call cdev_del(). Signed-off-by:
Rolf Eike Beer <eike-kernel@sf-tec.de> Cc: Alessandro Zummo <alessandro.zummo@towertech.it> Cc: Dmitry Torokhov <dtor@mail.ru> Signed-off-by:
-
Metathronius Galabant authored
It removes the awkwards spaces after the "=" when displaying the geometry of the attached volumes. Before: cciss: using DAC cycles blocks= 286734240 block_size= 512 heads= 255, sectors= 32, cylinders= 35139 After: cciss: using DAC cycles blocks=286734240 block_size=512 heads=255, sectors=32, cylinders=35139 Signed-off-by:Metathronius Galabant <m.galabant@gmail.com> Acked-by:
Mike Miller <mike.miller@hp.com> Signed-off-by:
-
Paul Fulghum authored
Increase maximum number of devices. Signed-off-by:
Paul Fulghum <paulkf@microgate.com> Signed-off-by:
-
Paul Fulghum authored
Add bisync and monosync serial protocol support to the synclink_gt driver. Signed-off-by:
-
Martin Schwidefsky authored
Use the new diagnose 0x9c in the spinlock implementation for s390. It yields the remaining timeslice of the virtual cpu that tries to acquire a lock to the virtual cpu that is the current holder of the lock. Signed-off-by:
Martin Schwidefsky <schwidefsky@de.ibm.com> Cc: Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Martin Schwidefsky authored
Powerpc already has a directed yield for CONFIG_PREEMPT="n". To make it work with CONFIG_PREEMPT="y" as well the _raw_{spin,read,write}_relax primitives need to be defined to call __spin_yield() for spinlocks and __rw_yield() for rw-locks. Acked-by:Paul Mackerras <paulus@samba.org> Signed-off-by:
-
Martin Schwidefsky authored
On systems running with virtual cpus there is optimization potential in regard to spinlocks and rw-locks. If the virtual cpu that has taken a lock is known to a cpu that wants to acquire the same lock it is beneficial to yield the timeslice of the virtual cpu in favour of the cpu that has the lock (directed yield). With CONFIG_PREEMPT="n" this can be implemented by the architecture without common code changes. Powerpc already does this. With CONFIG_PREEMPT="y" the lock loops are coded with _raw_spin_trylock, _raw_read_trylock and _raw_write_trylock in kernel/spinlock.c. If the lock could not be taken cpu_relax is called. A directed yield is not possible because cpu_relax doesn't know anything about the lock. To be able to yield the lock in favour of the current lock holder variants of cpu_relax for spinlocks and rw-locks are needed. The new _raw_spin_relax, _raw_read_relax and _raw_write_relax primitives differ from cpu_relax insofar that they have an argument: a pointer to the lock structure. Signed-off-by:
-
Paul Collins authored
I was playing with LED triggers when I noticed that changing from heartbeat (or ide-disk) to "none" at the right moment would leave the LED stuck on. This is easy to reproduce by doing "find / >/dev/null" with the ide-disk trigger enabled and then switching to "none". Here is a patch that fixes the problem by explicitly turning the LED off after removing the existing trigger. Signed-off-by:
Paul Collins <paul@ondioline.org> Acked-by:
Richard Purdie <rpurdie@rpsys.net> Signed-off-by:
-
Jim Cromie authored
Signed-off-by:
Jim Cromie <jim.cromie@gmail.com> Cc: Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Andrew Morton authored
Cc: David Woodhouse <dwmw2@infradead.org> Signed-off-by:
-
Alexey Dobriyan authored
Convert various spin_lock_irqsave() callers to correctly use `unsigned long'. Signed-off-by:
Alexey Dobriyan <adobriyan@gmail.com> Cc: Miles Bader <uclinux-v850@lsi.nec.co.jp> Cc: "Luck, Tony" <tony.luck@intel.com> Acked-by:
Kyle McMartin <kyle@mcmartin.ca> Cc: Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
Josef 'Jeff' Sipek authored
VFS: Use SEEK_{SET,CUR,END} instead of hardcoded values Signed-off-by:Josef 'Jeff' Sipek <jeffpc@josefsipek.net> Acked-by:
Trond Myklebust <trond.myklebust@fys.uio.no> Signed-off-by:
-
Josef 'Jeff' Sipek authored
EICON ISDN: Removed unused definitions for OS_SEEK_* Signed-off-by:
Armin Schindler <armin@melware.de> Signed-off-by:
-
Josef 'Jeff' Sipek authored
MBCS: Use SEEK_{SET,CUR,END} instead of hardcoded values Signed-off-by: -
Alan Cox authored
If we can clean up these remainders we can finally delete pci_find_* Signed-off-by:
Alan Cox <alan@redhat.com> Cc: Greg KH <greg@kroah.com> Acked-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Alan Cox authored
Mirrors the drivers/ata version, hold a reference to the host bridge while we are doing setup. Signed-off-by:
-
Alan Cox authored
As we don't support hotplug we end up leaking an isa_dev reference which if unload was ever added we would drop at the end of unloading. This is fine because we do genuinely need the isa_dev pointer until unload. Signed-off-by:
-
Alan Cox authored
Simple conversion Signed-off-by:
-
Alan Cox authored
Fairly trivial change in this case Signed-off-by:
-
Alan Cox authored
pci_find_device is not refcounting and should be getting killed off. Signed-off-by:
-
Ross Biro authored
The driver for /proc/config.gz consumes rather a lot of memory and it is in fact possible to build it as a module. In some ways this is a bit risky, because the .config which is used for compiling kernel/configs.c isn't necessarily the same as the .config which was used to build vmlinux. But OTOH the potential memory savings are decent, and it'd be fairly dumb to build your configs.o with a different .config. Signed-off-by:
Andrew Morton <akpm@google.com> Cc: "Randy.Dunlap" <rdunlap@xenotime.net> Cc: Sam Ravnborg <sam@ravnborg.org> Signed-off-by:
-
Cal Peake authored
Fix up kernel/sys.c to be consistent with CodingStyle and the rest of the file. Signed-off-by:
Cal Peake <cp@absolutedigital.net> Signed-off-by:
-
Alan Cox authored
Stop some other people peering into the baud bits on their own and make them use the tty_get_baud_rate() helper as a preperation for the move to the new termios. Corrected dependancy previous one had on new termios structs Signed-off-by:
-
Mike Miller (OS Dev) authored
Add support for logical volumes >2TB. All SAS/SATA controllers support large volumes. Signed-off-by:
-
Alexey Dobriyan authored
* fs/open.c is getting bit crowdy * preparation to lutimes(2) Signed-off-by:
-
Alexey Dobriyan authored
Signed-off-by:
-
Alexey Dobriyan authored
One of idiomatic ways to duplicate a region of memory is dst = kmalloc(len, GFP_KERNEL); if (!dst) return -ENOMEM; memcpy(dst, src, len); which is neat code except a programmer needs to write size twice. Which sometimes leads to mistakes. If len passed to kmalloc is smaller that len passed to memcpy, it's straight overwrite-beyond-end. If len passed to memcpy is smaller than len passed to kmalloc, it's either a) legit behaviour ;-), or b) cloned buffer will contain garbage in second half. Slight trolling of commit lists shows several duplications bugs done exactly because of diverged lenghts: Linux: [CRYPTO]: Fix memcpy/memset args. [PATCH] memcpy/memset fixes OpenBSD: kerberosV/src/lib/asn1: der_copy.c:1.4 If programmer is given only one place to play with lengths, I believe, such mistakes could be avoided. With kmemdup, the snippet above will be rewritten as: dst = kmemdup(src, len, GFP_KERNEL); if (!dst) return -ENOMEM; This also leads to smaller code (kzalloc effect). Quick grep shows 200+ places where kmemdup() can be used. Signed-off-by:
-
Takashi Iwai authored
Add maximum latency tracking to the ALSA subsystem for PCM playback. In ALSA, the playback application controls the buffer size and thus indirectly the period of latency that it can deal with. This patch uses 75% of the total available latency as threshold to announce to the latency subsystem; While 75% is a crude heuristic it's a quite reasonable one; the remaining 25% can be used for all driver processing for the next samples which is also proportional to the size of the buffer. With ogg123 a latency setting of about 4msec was seen (at 44Khz), while with the "play" command a much longer maximum tolerable latency was seen. Other, more multimedia oriented players as well as games, will have a lot smaller buffers to allow better synchronization and those will actually get into the latency domains where there is impact on the power management rules. Signed-off-by:
Takashi Iwai <tiwai@suse.de> Signed-off-by:
Arjan van de Ven <arjan@linux.intel.com> Signed-off-by:
-
Arjan van de Ven authored
Add infrastructure to track "maximum allowable latency" for power saving policies. The reason for adding this infrastructure is that power management in the idle loop needs to make a tradeoff between latency and power savings (deeper power save modes have a longer latency to running code again). The code that today makes this tradeoff just does a rather simple algorithm; however this is not good enough: There are devices and use cases where a lower latency is required than that the higher power saving states provide. An example would be audio playback, but another example is the ipw2100 wireless driver that right now has a very direct and ugly acpi hook to disable some higher power states randomly when it gets certain types of error. The proposed solution is to have an interface where drivers can * announce the maximum latency (in microseconds) that they can deal with * modify this latency * give up their constraint and a function where the code that decides on power saving strategy can query the current global desired maximum. This patch has a user of each side: on the consumer side, ACPI is patched to use this, on the producer side the ipw2100 driver is patched. A generic maximum latency is also registered of 2 timer ticks (more and you lose accurate time tracking after all). While the existing users of the patch are x86 specific, the infrastructure is not. I'd like to ask the arch maintainers of other architectures if the infrastructure is generic enough for their use (assuming the architecture has such a tradeoff as concept at all), and the sound/multimedia driver owners to look at the driver facing API to see if this is something they can use. [akpm@osdl.org: cleanups] Signed-off-by:
Ingo Molnar <mingo@elte.hu> Acked-by:
Jesse Barnes <jesse.barnes@intel.com> Cc: "Brown, Len" <len.brown@intel.com> Signed-off-by:
-
Richard Knutsson authored
Conversion of booleans to: generic-boolean.patch (2006-08-23) Signed-off-by:
Richard Knutsson <ricknu-0@student.ltu.se> Signed-off-by:
-
Richard Knutsson authored
Conversion of booleans to: generic-boolean.patch (2006-08-23) Signed-off-by:
-
Richard Knutsson authored
Conversion of booleans to: generic-boolean.patch (2006-08-23) Signed-off-by:
Anton Altaparmakov <aia21@cantab.net> Signed-off-by:
-
Richard Knutsson authored
This patch defines: * a generic boolean-type, named 'bool' * aliases to 0 and 1, named 'false' and 'true' Removing colliding definitions of 'bool', 'false' and 'true'. Signed-off-by:
-
Andrew Morton authored
- Add soothing comment - uninline thrice-called function Cc: OGAWA Hirofumi <hogawa@miraclelinux.com> Cc: Andi Kleen <ak@suse.de> Signed-off-by:
-
Keith Mannthey authored
The api for hot-add memory already has a construct for finding nodes based on an address, memory_add_physaddr_to_nid. This patch allows the fucntion to do something besides return 0. It uses the nodes_add infomation to lookup to node info for a hot add event. Signed-off-by:
Keith Mannthey <kmannth@us.ibm.com> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Cc: Andi Kleen <ak@muc.de> Signed-off-by:
-
