> > But distros can easily add the device id to their kernel if needed, it > > isn't something that the -stable tree shoud be accepting. Otherwise, we > > will be swamped with those types of patches... > > > > Oh sure, leave the distros swamped with them instead. :) > > And they all have to do it separately, meaning they don't stay in sync > and they duplicate each other's work... Well they *don't* have to work that separately. They could set up some shared tree which would look suspiciously like what Greg is doing but with the ID updates.... ;) - 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/
- Follow-Ups:
- References:
- 2.6.22 -mm merge plans
- From: Andrew Morton <[email protected]>
- to something appropriate (was Re: 2.6.22 -mm merge plans)
- From: Jeff Garzik <[email protected]>
- Re: to something appropriate (was Re: 2.6.22 -mm merge plans)
- From: Andrew Morton <[email protected]>
- Re: to something appropriate (was Re: 2.6.22 -mm merge plans)
- From: Jeff Garzik <[email protected]>
- Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans)
- From: Chris Wright <[email protected]>
- Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans)
- From: Jeff Garzik <[email protected]>
- Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans)
- From: Greg KH <[email protected]>
- Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans)
- From: Chuck Ebbert <[email protected]>
- 2.6.22 -mm merge plans
- Prev by Date: Re: [Kernel-discuss] Re: [RFC, PATCH 0/4] SoC base drivers
- Next by Date: Re: [linux-dvb] Re: DST/BT878 module customization (.. was: Critical points about ...)
- Previous by thread: Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans)
- Next by thread: Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans)
- Index(es):