- 09 Aug, 2005 2 commits
-
-
John McCutchan authored
This removes the now unused fsnotify_unlink & fsnotify_rmdir code. Compile tested. Signed-off-by:
John McCutchan <ttb@tentacle.dhs.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Linus Torvalds authored
Revert commit fec59a71, which is breaking sparc64 that doesn't have a working pci_update_resource. We'll re-do this after 2.6.13 when we'll do it all properly.
-
- 08 Aug, 2005 16 commits
-
-
Dave Jones authored
Fix a null dereference in module unload path. Found by a simple modprobe icn ; rmmod icn Signed-off-by:
Dave Jones <davej@redhat.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
Linus Torvalds authored
-
Olaf Hering authored
modprobe aes does not work on x86_64. i386 has a similar line, this could be the right fix. Would be nice to have in 2.6.13 final. Signed-off-by:
Olaf Hering <olh@suse.de> Signed-off-by:
-
Kumar Gala authored
The memory mappings for MPC8349 USB MPH and DR modules were reversed. Signed-off-by:
Li Yang <LeoLi@freescale.com> Signed-off-by:
Jiang Bo <Tanya.jiang@freescale.com> Signed-off-by:
Kumar Gala <kumar.gala@freescale.com> Signed-off-by:
-
Heikki Orsila authored
Here's a small patch to cleanup NETDEBUG() use in net/ipv4/ for Linux kernel 2.6.13-rc5. Also weird use of indentation is changed in some places. Signed-off-by:
Heikki Orsila <heikki.orsila@iki.fi> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
David S. Miller authored
NETLINK_ARPD is unused, allocate it to the Open-iSCSI folks. NETLINK_ROUTE6 and NETLINK_TAPBASE are no longer used, delete them. Signed-off-by: -
Linus Torvalds authored
-
John McCutchan authored
The patch below unhooks fsnotify from vfs_unlink & vfs_rmdir. It introduces two new fsnotify calls, that are hooked in at the dcache level. This not only more closely matches how the VFS layer works, it also avoids the problem with locking and inode lifetimes. The two functions are - fsnotify_nameremove -- called when a directory entry is going away. It notifies the PARENT of the deletion. This is called from d_delete(). - inoderemove -- called when the files inode itself is going away. It notifies the inode that is being deleted. This is called from dentry_iput(). Signed-off-by:
-
Michael Krufky authored
- Structural changes within lgdt330x driver, framework now supports both chips... tested OK on lgdt3302 and lgdt3303. - Add LG/TUA6034 dvb_pll_desc for ATSC with LG TDVS-H062F & DViCO FusionHDTV5. - Fixed LGDT330X signal strength: For now, always set it to 0. - Corrected LGDT330X boundary condition error in read_snr: dB calculation. Signed-off-by:
Mac Michaels <wmichaels1@earthlink.net> Signed-off-by:
Michael Krufky <mkrufky@m1k.net> Signed-off-by:
-
Cornelia Huck authored
From: Martin Schwidesky <schwidefsky@de.ibm.com> Convert qeth to the new klist interface and make it compiling again. Signed-off-by:
Frank Pavlic <pavlic@de.ibm.com> Signed-off-by:
-
Harald Welte authored
With the introduction of 'rustynat' in 2.6.11, the old tricks of preventing NAT of 'untracked' connections (e.g. NOTRACK target in 'raw' table) are no longer sufficient. The ip_conntrack_untracked.status |= IPS_NAT_DONE_MASK effectively prevents iteration of the 'nat' table, but doesn't prevent nat_packet() to be executed. Since nr_manips is gone in 'rustynat', nat_packet() now implicitly thinks that it has to do NAT on the packet. This patch fixes that problem by explicitly checking for ip_conntrack_untracked in ip_nat_fn(). Signed-off-by:
Harald Welte <laforge@netfilter.org> Signed-off-by:
-
James Morris authored
-
Ivan Kokshaysky authored
Like many other southbridges from different manufacturers, VIA VT8235 chip has two non-standard BARs for power management and SMBus registers (see the datasheet at http://www.via.com.tw). This new quirk routine fixes boot problem with 2.6.13-rc2/rc6 kernels on Targa Visionary 811 Athlon64 laptop, as reported by Mikael Pettersson <mikpe@csd.uu.se>. Signed-off-by:
Ivan Kokshaysky <ink@jurassic.park.msu.ru> Signed-off-by:
-
Antonino Daplas authored
Reported by:Vincent Fortier (Bugzilla Bug 4768) "At boot time the screen appears moved to the mid right portion of the actual video pannel making the end of the line appears at the left edge... It simply looks like moved half way to the right" His particular hardware has a display with an unusual dimension (1920x1200) but unfortunately has no EDID block. None of the entries in the global mode database is correct for this particular display, and it particularly has difficulty scaling up 640x480 (the default startup mode of nvidiafb) to 1920x1200 which causes the above described problem. 1, Add 1920x1200 to the global mode database. 2. Let nvidiafb base the startup mode from the flatpanel dimensions only if the EDID block is absent, no boot mode parameter is specified by the user, and a flatpanel/LCD display is attached. Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Paul Mackerras authored
Update the default/example configs for ppc64. Pretty boring... Signed-off-by:
Paul Mackerras <paulus@samba.org> Signed-off-by:
-
Arnd Bergmann authored
This adds a bpa_defconfig file and make target. The config settings are made for the current version of the Cell Processor Based Blade, so there are not too many drivers enabled. A few more drivers might get added in the future though. Signed-off-by:
Arnd Bergmann <arndb@de.ibm.com> Signed-off-by:
-
- 07 Aug, 2005 19 commits
-
-
Linus Torvalds authored
Last (?) -rc, partly brought on by the aic7xxx performance fixes (ie get them tested in an -rc release before the real 2.6.13).
-
Dominik Hackl authored
This patch fixes a typo in lib/crc32.c which results in incorrect debug output. Signed-off-by:
Dominik Hackl <dominik@hackl.dhs.org> Signed-off-by:
-
Ravikiran G Thirumalai authored
Move the fix to align node_end_pfns to a proper location. The earlier fix made the node_remap_start_vaddr to get misaligned causing remap_numa_kva to barf again :-/ Signed-off-by:
Ravikiran Thirumalai <kiran@scalex86.org> Signed-off-by:
Shai Fultheim <shai@scalex86.org> Signed-off-by:
-
Marcelo Tosatti authored
Touching the pte directly causes the 8Mbyte TLB entry to be invalidated. This has been fixed in v2.4 for ages. Signed-off-by:
Marcelo Tosatti <marcelo.tosatti@cyclades.com> Signed-off-by:
-
Aristeu Sergio Rozanski Filho authored
8xx: commproc.c: kill unused variable Signed-off-by:
Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org> Signed-off-by:
-
Aristeu Sergio Rozanski Filho authored
8xx: restrict ENET_BIG_BUFFERS option to drivers which actually use it Signed-off-by:
-
Aristeu Sergio Rozanski Filho authored
8xx: fix CPM Ethernet description Signed-off-by:
-
Aristeu Sergio Rozanski Filho authored
8xx: fec: fix interrupt handler prototypes Signed-off-by:
Aristeu Sergio Rozanski Filho <aris@conectiva.com.br> Signed-off-by:
-
Aristeu Sergio Rozanski Filho authored
8xx: using dma_alloc_coherent() instead consistent_alloc() Signed-off-by:
-
Aristeu Sergio Rozanski Filho authored
8xx: convert fec driver to use work_struct Signed-off-by:
-
Miklos Szeredi authored
I'm resending this patch, because I still believe it's the correct fix. Tested before/after applying the patch with a test application available from: http://www.inf.bme.hu/~mszeredi/nstest.c Bind mount from a foreign namespace results in an un-removable mount. The reason is that mnt->mnt_namespace is copied from the old mount in clone_mnt(). Because of this check_mnt() in sys_umount() will fail. The solution is to set mnt->mnt_namespace to current->namespace in clone_mnt(). clone_mnt() is either called from do_loopback() or copy_tree(). copy_tree() is called from do_loopback() or copy_namespace(). When called (directly or indirectly) from do_loopback(), always current->namspace is being modified: check_mnt(nd->mnt). So setting mnt->mnt_namespace to current->namspace is the right thing to do. When called from copy_namespace(), the setting of mnt_namespace is irrelevant, since mnt_namespace is reset later in that function for all copied mounts. Jamie said: This patch is correct. The old code was buggy for more fundamental and serious reason: it broke the invariant that a tree of vfsmnts all have the same value of mnt_namespace (and the same for the mnt_list list). Signed-off-by:
Miklos Szeredi <miklos@szeredi.hu> Acked-by:
Jamie Lokier <jamie@shareable.org> Cc: <viro@parcelfarce.linux.theplanet.co.uk> Cc: Christoph Hellwig <hch@lst.de> Signed-off-by:
-
Olaf Hering authored
sparc can not include linux/pagemap.h because of the following circular dependency: asm-sparc/pgtable include linux/swap.h linux/swap.h include now linux/pagemap.h linux/pagemap.h include linux/mm.h linux/mm.h include asm/pgtable.h It needs to have the swp_entry_t type fully visible in pgtable.h, we can't work around this using macros. Signed-off-by:
-
Tom Duffy authored
This patch add stubs to allow the visws subarch to link again. Signed-off-by:
Tom Duffy <thomas.duffy.99@alumni.brown.edu> Signed-off-by:
-
Tom Duffy authored
In file included from linux-2.6.13-rc5/arch/i386/kernel/timers/timer_pit.c:20: linux-2.6.13-rc5/include/asm-i386/mach-visws/do_timer.h: In function `do_timer_overflow': linux-2.6.13-rc5/include/asm-i386/mach-visws/do_timer.h:32: error: `i8259A_lock' undeclared (first use in this function) linux-2.6.13-rc5/include/asm-i386/mach-visws/do_timer.h:32: error: (Each undeclared identifier is reported only once linux-2.6.13-rc5/include/asm-i386/mach-visws/do_timer.h:32: error: for each function it appears in.) make[3]: *** [arch/i386/kernel/timers/timer_pit.o] Error 1 make[2]: *** [arch/i386/kernel/timers] Error 2 make[1]: *** [arch/i386/kernel] Error 2 make: *** [_all] Error 2 Signed-off-by:
-
Andrew Morton authored
Remove a very wrong comment. Signed-off-by:
-
Andi Kleen authored
Don't log machine check events left over from boot. Too many BIOSes leave bogus events in there. This unfortunately also makes it impossible to log events that caused a reboot. For people with non broken BIOS there is mce=bootlog Signed-off-by:
Andi Kleen <ak@suse.de> Signed-off-by:
-
Ivan Kokshaysky authored
For 64-bit BAR[i] only pci_dev->resource[i] is valid, ->resource[i+1] slot is unused and contains zeroes in all fields. So when we update a PCI BAR, all we need is just to check that we're going to update a _valid_ resource. Also make sure to write high bits - use "x >> 16 >> 16" (rather than the simpler ">> 32") to avoid warnings on 32-bit architectures where we're not going to have any high bits. Signed-off-by: -
Christoph Hellwig authored
Doesn't make the local irq disabling around it less buggy, but at least we replace the offender with the right kind of primitive. Signed-off-by:
Christoph Hellwig <hch@lst.de> Signed-off-by:
Russell King <rmk+kernel@arm.linux.org.uk>
-
Russell King authored
This function produces a warning when CPU_FREQ=n. Since it's a very simple calculation, make it inline instead of adding preprocessor directives around it. Signed-off-by:
-
- 06 Aug, 2005 3 commits
-
-
Eric W. Biederman authored
When the sparse mem changes and the kexec changes were merged into setup.c they came in, in the wrong order. This patch changes the order so we don't run sparse_init which uses the bootmem allocator until we all of the reserve_bootmem calls has been made. Signed-off-by:
Eric W. Biederman <ebiederm@xmission.com> Signed-off-by:
-
Eric W. Biederman authored
Another x86 subarchitecture bit I missed. This adds both machine_emergency_restart missed in my reboot fixes and machine_shutdown needed for kexec support. Signed-off-by: -
Eric W. Biederman authored
Here is one more bit of breakage my x86 sub-architecture confusion caused. Add machine_shutdown to voyager so it will compile with CONFIG_KEXEC. Signed-off-by:
-
