On Fri, May 06, 2005 at 01:10:09AM -0700, Chris Wright wrote: > * Andries Brouwer ([email protected]) wrote: > > No, there is no problem but an intentional change in behaviour in -mm > > and now also in 2.6.11.8. > > I think this should be backed out of -stable. I agree, I'll go do it in the tree right now, sorry about this. greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Empty partition nodes not created (was device node issues with recent mm's and udev)
- From: Joe <[email protected]>
- Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
- From: Greg KH <[email protected]>
- Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
- From: "Randy.Dunlap" <[email protected]>
- Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
- From: Andries Brouwer <[email protected]>
- Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
- From: Chris Wright <[email protected]>
- Empty partition nodes not created (was device node issues with recent mm's and udev)
- Prev by Date: 2.6.11.7 apparently locked with xscreensaver, 2.6.11.7
- Next by Date: best practise for ioremap / ioremap_nocache / MTRR
- Previous by thread: Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
- Next by thread: Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
- Index(es):
 |