On Mon, Jan 14, 2008 at 09:21:32AM -0800, Kevin Lloyd wrote: > > Hm, no, the intrusion into the driver is just too much this late in > the > > release cycle to allow this. > > > > Now I will be glad to only add the new device ids for the devices that > > do not rely on the new changes right now, but that's it. > > > > So, right now I have a separate patch split out of your original one > > that is below. Should I modify it and not include some of these > device > > ids right now? You mention 0023, is that the only one I should remove > > from this patch? > > Correct, the 0x0023 is the only newly added device that requires the new > features.
Does that mean things will not work for this device if it is added to the device table, without the code updates? And is this device even public yet? > When do you expect the other changes will be propagated to the kernel? > Would it be in a 2.6.24.x point release or will they have to wait until > 2.6.25? They will have to wait until 2.6.25, they are too big to go into 2.6.24 (we are in severe bug-fix mode only right now for .24). thanks, 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/
