Well, my intention is to list the most recent regressions in these messages. Your regression is in the bugzilla, is marked as a regression and linked to the appropriate meta bug entry ... Well, perhaps I'll be able to send a "post 2.6.22 regressions" message with a longer list from time to time, but I can't promise that. Greetings, Rafael -

2.6.23 did not have pata_acpi. Its also not clear this is a bug in pata_acpi as opposed to pata_ali which knows about the ALi quirks. The ACPI and ATA specs sort of disagree here so I'll be trying to fix it anyway. -

To quote lolcats: CONFIG_RESOURCES_64BIT DO NOT WANT! I *think* I have the logic of this right... Anyway, I was annoyed by having to do the bloody ugly casts to unsigned long long in arch-specific code. As near as I can tell, we only want this selectable in the case of PAE on x86, and some random PPC and MIPS embedded boards. For everyone else, it should be whatever the value of 64BIT is. And I can be happy and continue using unsigned long and going about my merry business. Signed-off-by: Ky...

Sergey S. Kostyliov <rathamahata@gmail.com> : It should reappear after some time at rest. Until I come with something better, you should use 2.6.24-rc with the r8169 driver from 2.6.23. -- Ueimor -

This message is added by klogd, and it is independent of CONFIG_KALLSYMS. (Since I do have KALLSYMS=y while also getting that message. I suppose it is because CONFIG_DEBUG_INFO=n) -

Like I said, klogd. This seems to be outside the scope of LKML. -

Just a note on the attribute((acquire,release)) proposal: It's nice to be able to annotate functions, but please don't forget to provide a way to write such functions. Ultimately, there will be an asm() or assignment that is the acquire or release point, and GCC needs to know that so it can compile the function itself (possibly inline). Having just a function attribute leaves the problem that void __attribute__((noreturn)) _exit(int status) { asm("int 0x80" : : (__NR_exit) "a", (status) "b"...

http://marc.info/?i=1193419828.3293.35.camel@localhost.localdomain -

From: Bradley Smith <bradjsmith@btinternet.com> Adds i8k driver to the x86_64 Kconfig. Signed-off-by: Bradley Smith <bradjsmith@btinternet.com> --- Only applies on kernels >= 2.6.24. Depends on "[PATCH 1/2] I8K: Allow i8k driver to be built on x86_64 systems" --- linux-2.6/arch/x86/Kconfig.x86_64.orig 2007-10-28 14:04:13.000000000 +0000 +++ linux-2.6/arch/x86/Kconfig.x86_64 2007-10-28 13:59:06.000000000 +0000 @@ -224,6 +224,26 @@ config X86_GOOD_APIC bool default y ...

On Sun, 28 Oct 2007 18:46:40 +0100 I was going by linux-2.6/arch/x86/Kconfig.i386, which has "config I8K" but maybe it should be changed... Brad. -

Is this actually known to be working on a Dell laptop? Jeff -

Please use CONFIG_X86_64. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -

Sorry, my mail client corrupted the previous mail containing the patch... it should be ok now... Add a boot parameter (‘pci-mem-align’) which forces PCI memory regions to be aligned to 4K. This is very useful when developing an hypervisor, since in case we want to let native domains direct access to specific hardware, we don’t want PCI devices to share their memory region page with other devices. In Xen for example, PCI devices mmio resources are mapped by remapping complete pages (by Intel VT-...

Please follow the proper coding style rules as documented in Documentation/CodingStyle. Also running the script scrips/checkpatch.pl All command line paramaters need to be documented in the Documentation Now for the main reason. I really don't understand why this is needed. Is it only for virtual machines? Are there drivers in the kernel tree today that need this functionality? What breaks if you do not align these resources? thanks, greg k-h -

But doesn't aligning such regions on that alignment break some devices as that is not what the device is asking for in the BIOS? And if not, why would we not do this for all devices not just for virtual machines, if it is such a benefit? Also, how does this play with the hardware IOMMU chips that provide such virtualization in hardware for you? And, we can't accept a patch for 2.6.18, there is no development tree to apply it to anymore, that is a dead kernel tree. It needs to be against 2.6...

Hi, This patch is oddly double-spaced and space-stuffed (spaces instead of tabs). Likely a mail client doing this. It's usually a good idea to send patches to yourself to make sure that they will --- ~Randy -

>>>>> "Jacopo" == jack <jack@antonello.org> writes: Jacopo> this patch implements a macbook like backlight dimmer on top Jacopo> of backlight.c. Jacopo, if you want your patch to be reviewed, you should first put it in an acceptable form. You can start by running it through scripts/checkpatch.pl. Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/ -

On Sun, 28 Oct 2007 22:30:55 +0100 hi, when going over your patch.. is there a reason you introduce yet another timeout infrastructure? Is there something wrong with the existing ones that maybe should be fixed instead? Either way.. please put justification for such new mechanism in the patch changelog.... Greetings, Arjan van de Ven -- If you want to reach me at my work email, use arjan@linux.intel.com For development, discussion and tips for power savings, visit [ message continues ]

Hello, I get the following output from the command "make install" after the source files were successfully compiled for my personal configuration. if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map 2.6.23.1-default; fi sh /usr/src/linux-2.6.23.1/arch/i386/boot/install.sh 2.6.23.1-default arch/x86_64/boot/bzImage System.map "/boot" Kernel image: /boot/vmlinuz-2.6.23.1-default Initrd image: /boot/initrd-2.6.23.1-default Root device: /dev/system/root (mounted on ...

I have assumed that my Linux distribution is clean enough to try out a current kernel. Would you like to recommend anything to get rid from these warnings about unresolved dependencies? Regards, Markus -

I intentionally omitted the configuration option "DM_SNAPSHOT" because it is marked as "EXPERIMENTAL". Snapshot target: "Allow volume managers to take writable snapshots of a device." I intentionally checked the option "BLK_DEV_SD". I do not want to build it as a module. SCSI disk support: "If you want to use SCSI hard disks, Fibre Channel disks, Serial ATA (SATA) or Parallel ATA (PATA) hard disks, USB storage or the SCSI or parallel port version of the IOMEGA ZIP drive, say Y and read the SCSI...

Hmm... http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=c9d00f... -> Adds !PM because suspend was broken (17.11.2005) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=7931e1... -> Adds suspend support, but fails to remove the !PM (5.12.2005) So it looks like that !PM is false. I have the following device: Bus 001 Device 005: ID 1058:0400 Western Digital Technolog...

This patch removes obviously dead code. Signed-off-by: Adrian Bunk <bunk@kernel.org> --- drivers/scsi/seagate.c | 2 -- 1 file changed, 2 deletions(-) c0807bbefb65ef679b7d2ec13d14c35f2e927404 diff --git a/drivers/scsi/seagate.c b/drivers/scsi/seagate.c index b113244..2d31ed4 100644 --- a/drivers/scsi/seagate.c +++ b/drivers/scsi/seagate.c @@ -1437,17 +1437,15 @@ connect_loop: break; #ifdef LINKED case LINKED_WRONG: WRITE_DATA (ABORT); linked_connecte...

This patch removes dead code spotted by the Intel C Compiler. Signed-off-by: Adrian Bunk <bunk@kernel.org> --- drivers/ieee1394/ieee1394_transactions.c | 2 -- 1 file changed, 2 deletions(-) 0df395c3e17cd6ac7176707a33580a1836db8bdf diff --git a/drivers/ieee1394/ieee1394_transactions.c b/drivers/ieee1394/ieee1394_transactions.c index c39c70a..6779893 100644 --- a/drivers/ieee1394/ieee1394_transactions.c +++ b/drivers/ieee1394/ieee1394_transactions.c @@ -208,108 +208,106 @@ void h...

The timer code always calls the clock_event_device set_net_event and set_mode methods with interrupts disabled, so no need to use spin_lock_irqsave / spin_unlock_irqrestore for those. arch/mips/kernel/i8253.c | 12 ++++-------- arch/x86/kernel/i8253.c | 12 ++++-------- 2 files changed, 8 insertions(+), 16 deletions(-) diff --git a/arch/mips/kernel/i8253.c b/arch/mips/kernel/i8253.c index 5d9830d..1b54674 100644 --- a/arch/mips/kernel/i8253.c +++ b/arch/mips/kernel/i8253.c @@ -23,9 +23,7...