Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262520AbVCDHEc (ORCPT ); Fri, 4 Mar 2005 02:04:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262565AbVCDHEc (ORCPT ); Fri, 4 Mar 2005 02:04:32 -0500 Received: from fire.osdl.org ([65.172.181.4]:24236 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S262520AbVCDHE1 (ORCPT ); Fri, 4 Mar 2005 02:04:27 -0500 Date: Thu, 3 Mar 2005 23:04:18 -0800 From: Chris Wright To: Andrew Morton Cc: Chris Wright , jgarzik@pobox.com, olof@austin.ibm.com, paulus@samba.org, rene@exactcode.de, torvalds@osdl.org, linux-kernel@vger.kernel.org, greg@kroah.com Subject: Re: [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec Message-ID: <20050304070418.GQ5389@shell0.pdx.osdl.net> References: <20050303225542.GB16886@austin.ibm.com> <20050303175951.41cda7a4.akpm@osdl.org> <20050304022424.GA26769@austin.ibm.com> <20050304055451.GN5389@shell0.pdx.osdl.net> <20050303220631.79a4be7b.akpm@osdl.org> <4227FC5C.60707@pobox.com> <20050304062016.GO5389@shell0.pdx.osdl.net> <20050303222335.372d1ad2.akpm@osdl.org> <20050304064759.GP5389@shell0.pdx.osdl.net> <20050303225445.165f34da.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050303225445.165f34da.akpm@osdl.org> User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1222 Lines: 34 * Andrew Morton (akpm@osdl.org) wrote: > Chris Wright 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. > > 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/