* Greg KH <[EMAIL PROTECTED]> wrote: > > but we only have cpu_clock() from v2.6.23 onwards - so we should not > > apply the original patch to v2.6.22. (we should not have applied > > your patch that started the mess to begin with - but that's another > > matter.) > > Well, I can easily back that one out, if that is easier than adding 2 > more patches to try to fix up the mess here. > > Let me know if you feel that would be best.
i'd leave it alone - doing that we have in essence the softlockup detector turned off. Reverting to the older version might trigger false positives that need the new stuff. Ingo - 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/