Prev: [PATCH] x86: fpu xstate fix memory poison overwritten
Next: object: is not initialized, yet kobject_put() is being called
From: Fred . on 12 Aug 2010 07:30 BKL is a long standing issue with the kernel. There are patches for it, why arent they merged? Merge the patches! Fix the BKL, its about time! http://kernelnewbies.org/BigKernelLock -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Sam Ravnborg on 12 Aug 2010 08:40
On Thu, Aug 12, 2010 at 01:20:44PM +0200, Fred . wrote: > BKL is a long standing issue with the kernel. > > There are patches for it, why arent they merged? > Merge the patches! > > Fix the BKL, its about time! > > http://kernelnewbies.org/BigKernelLock It has not occurred to you that referred status is not quite up-to-date? During this merge window a lot of BKL removal patches has been merged. I guess LWN will followup with some sort of status on their kernel page when the merge window has closed. Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |