Prev: [PATCH] xen: ensure timer tick is resumed even on CPU driving the resume
Next: mm: Move ARCH_SLAB_MINALIGN and ARCH_KMALLOC_MINALIGN to <linux/slab_def.h>
From: H. Peter Anvin on 19 May 2010 16:10 On 05/19/2010 12:03 PM, Frederic Weisbecker wrote: >> >> But it's not ... it is locked at that point. It's not lock*ing*, but it >> is not *unlocked*, either. Furthermore, it is directly contradicting >> the naming scheme of the ops structure. >> > > Would you prefer me to resend a patch? > Yes, that would be my preference. We really need to set a date to kill off autofs3 completely -- I don't care if we rename anything or not -- and add it to feature-removal.txt. -hpa -- 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: Ian Kent on 20 May 2010 07:50
On Wed, 2010-05-19 at 13:04 -0700, H. Peter Anvin wrote: > On 05/19/2010 12:03 PM, Frederic Weisbecker wrote: > >> > >> But it's not ... it is locked at that point. It's not lock*ing*, but it > >> is not *unlocked*, either. Furthermore, it is directly contradicting > >> the naming scheme of the ops structure. > >> > > > > Would you prefer me to resend a patch? > > > > Yes, that would be my preference. > > We really need to set a date to kill off autofs3 completely -- I don't > care if we rename anything or not -- and add it to feature-removal.txt. Yes, my bad. I have to get onto that, sorry. Ian -- 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/ |