- 06 Oct, 2004 40 commits
-
-
Maximilian Attems authored
s/for/list_for_each/ Signed-off-by:
Domen Puncer <domen@coderock.org> Signed-off-by:
Maximilian Attems <janitor@sternwelten.at> Signed-off-by:
Greg Kroah-Hartman <greg@kroah.com>
-
Maximilian Attems authored
Change for loops with list_for_each_entry(). Signed-off-by:
-
Maximilian Attems authored
Change for loops with list_for_each(). Signed-off-by:
-
Maximilian Attems authored
Replace for with more readable list_for_each. Compile tested. Signed-off-by:
-
Li Shaohua authored
On Tuesday, August 31, 2004, Linus Torvalds wrote: > That list per se obviously looks ok by me, although I'd worry that some > other fs_initcall depends on the ACPI stuff having been run (ie while the > abover ordering is great, I worry that some _other_ part doesn't fit in > the above ordering). Doing a quick check finds "chr_dev_init()", for > example, which will do fbmem_init(), which might depend on the ACPI/PnP > stuff having run already. > > So it _might_ be safer to make this ordering more explicit, rather than Yes, I agree. The problem is there isn't a straightforward method for it. It possibly is hard to get it. > depending on the different phases of the initcalls. But I'd happily be > proven wrogn with some simple argument for why this is guaranteed to be > ok.. For example, maybe ACPI and PnP is linked before chr/mem.c, in which > case it should all be ok. Original PCI assign resources code is the last 'subsys_initcall' according to the makefile, so move some code of it to 'fs_initcall' (just below 'subsystem_initcall') should be ok. As you said, ACPI and PnP is linked before chr/mem.c. The method requires all other 'fs_initcall' don't touch PCI resources, since 'pcibios_assign_resources' is a 'fs_initcall' and maybe don't run, but it looks ok currently. Again, I will be appreciated if we can find a solution to make the ordering explicit. Signed-off-by: -
David Brownell authored
That document was wrong on some things, misleading on others; this fixes some of the issues I noticed. However it probably needs to say that drivers for devices that implement the PCI PM spec "should" always use pci_set_power_state() to reduce the power usage. If I get ambitions I might submit a patch to the PCI core to print a nag message for drivers that don't do that. Updates the PCI PM docs, better matching the specs and code. - List both D3 states (D3hot, D3cold) up front. - Clarify that suspend() methods should disable I/0 (including DMA) and IRQs; it's not optional. - More accurately describe resume(); there are common cases where device re-initialization isn't appropriate. The previous text said re-init was always required; that's false. Signed-off-by:David Brownell <dbrownell@users.sourceforge.net> Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by: -
Evgeniy Polyakov authored
Remove pci_find_device() in arch/i386/kernel/scx200.c. Signed-off-by:
Evgeniy Polyakov <johnpol@2ka.mipt.ru> Signed-off-by:
-
Greg Kroah-Hartman authored
Thanks to Joe Perches for pointing this out. Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Use pci_get_subsys() if you want this functionality. Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Signed-off-by: -
Linus Torvalds authored
-
Paolo \'Blaisorblade\' Giarrusso authored
Change the spacing for this command to fix alignment on output. Signed-off-by:
Paolo 'Blaisorblade' Giarrusso <blaisorblade_spam@yahoo.it> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Paolo \'Blaisorblade\' Giarrusso authored
Remove uml.lds and dyn.lds from extra-y; this was a relict from the recent past. Signed-off-by:
-
Hirokazu Takata authored
Remove obsolete m32r-specific driver files, which are no longer used. Signed-off-by:
Hirokazu Takata <takata@linux-m32r.org> Signed-off-by:
-
Hirokazu Takata authored
Signed-off-by:
-
Hirokazu Takata authored
Signed-off-by:
-
Christoph Hellwig authored
completely unused wrapper Signed-off-by:
-
Christoph Hellwig authored
this is a 2.4ish block driver that doesn't have the slightest chance to actually build. It's also not connected to the build at all. Signed-off-by:
-
Hirokazu Takata authored
Here is a patch to update ioremap*.c for m32r, taken from "Add __iomem modifier to the return value type of __ioremap() for much stricter type-checking." * arch/m32r/mm/ioremap.c: ditto. - Add __iomem modifier to the return value type of __ioremap() for much stricter type-checking. * arch/m32r/mm/ioremap-nommu.c: ditto. * include/asm-m32r/io.h: - Modified for much stricter type-checking. - Change __inline__ to inline. Signed-off-by:
-
Andi Kleen authored
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com> Fix off by one in TSS limit. Signed-off-by:
Andi Kleen <ak@suse.de> Signed-off-by:
-
Andi Kleen authored
(cosmetic) print newline before MCEs Signed-off-by:
-
Suresh B. Siddha authored
Set TARGET_CPUS on x86_64 to cpu_online_map. This brings the code inline with x86 mach-default. Fix MSI_TARGET_CPU code which will break with this target_cpus change. Signed-off-by:
Suresh Siddha <suresh.b.siddha@intel.com> Signed-off-by:
-
Andi Kleen authored
x86-64 in_gate_vma would take a read lock on the VMA when the passed address was inside the 32bit vsyscall page. This would be called by get_user_pages, which already holds the mmap_sem. Unfortunately some callers of get_user_pages hold the mmap_sem for writing, which could in theory cause a deadlock. I think it can currently not happen because the only users who hold it for write before calling gup() are coredump and AIO in the ring setup, and both should not ever access the vsyscall page. But not taking the semaphore is safer and avoid this here. Signed-off-by:
-
Andi Kleen authored
Don't corrupt interrupt flag in time resume Signed-off-by:
-
Andi Kleen authored
Avoid a deadlock during panic. Don't take the smp_call_function lock in smp_send_stop() Also fix the documentation to conform to Linux standards. Signed-off-by:
-
Andi Kleen authored
Fix a circular dependency Signed-off-by:
-
Andi Kleen authored
CONFIG_FRAME_POINTER has never worked on x86-64 because it never passed -fno-omit-frame-pointer to the compiler, and that is the only way to get a frame pointer on x86-64. It also causes complications with profiling. Drop it. Signed-off-by:
-
Andi Kleen authored
This fixes profile_pc to work properly on x86-64 and not crash. It does now a simple backtrace to the caller of the spin lock without requiring a frame pointer for this. Frame pointer support has been dropped because it never worked. There is still a small race window, but the only way to avoid it would be to rewrite kernel/spinlock.c in assembler again. The race will account a profile tick the the parent of the spinlock caller. Signed-off-by:
-
Andi Kleen authored
Fix oops when multiple MCE entries are logged. Signed-off-by:
-
Andi Kleen authored
From: <mg@iceni.pl> The following patch fixes compilation of time.c with HPET_HACK_ENABLE_DANGEROUS turned on. Signed-off-by:
-
David Gibson authored
arch/ppc64/kernel/process.c has an #ifdef CONFIG_ALTIVEC within an #ifdef CONFIG_ALTIVEC. This patch removes the inner one. Signed-off-by:
David Gibson <david@gibson.dropbear.id.au> Signed-off-by:
-
