On Sat, Feb 20, 2010 at 12:59:25PM -0600, Larry Finger wrote: > On 02/20/2010 12:31 PM, Kalle Valo wrote: > > "John W. Linville" <linville@xxxxxxxxxxxxx> writes: > > > >> Since I've got the 'offending' commit in my tree, I'll carry this > >> staging fixup as well... > > > > And I was the one who broke this, sorry. What's the general rule for > > this, should I also start compile testing staging drivers when > > changing something? > > As someone else that was hit by this problem, I think that is a good idea. I > realize that staging drivers are a special case, but it is likely easier for the > person changing the ABI to fix any breakage. In addition, if the fixes are > entered at the same time as the original change, there will not be any build > breakage during bisection, and any questions of which coordinator to use will be > avoided. Ideally, yes, you should also fix up the staging drivers. But in reality, no, I do not expect you, or anyone else to do so. If it causes you extra hassles and work, do not worry about anything in drivers/staging/ I will handle that. I can handle api changes just fine, it's not all that hard :) So don't worry about it. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
