> Is there a specific patch that fixes this issue that is not around? Or > is it already in my staging-next tree and you feel it should be added to > the final .36 release? > > If so, which one is it? > > thanks, > > greg k-h > for the build problem, include it in 2.6.36 no need for more delay.