* Andrew Morton ([EMAIL PROTECTED]) wrote: > Chris Wright <[EMAIL PROTECTED]> wrote: > > > > > And it's a temp-fix - it'll be addressed by other means in 2.6.12. > > > > > > What do we do? > > > > IMO, we have to rely on Dmitry's judgement. Is it critical (i.e. broke > > laptops how)? Can it be worked around with the i8042.noacpi boot param? > > If so, I don't think it fits the bill as critical. > > Well. It was critical for 2.6.11, but it didn't make it :(
Ah, I see. > So people whose keyboards don't work need to either update to 2.6.11.1 or > add i8042.noacpi=1. <rekicks self> > > But it's just a for-instance. And a good one to exercise the rules measuring how critical the patch is. In this case, I don't think it is if workaround is good enough, but could be convinced if Dmitry thinks otherwise. Anyway, time to pack, sleep a few and catch a plane back west later, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net - 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/
