Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758908AbYJIMUM (ORCPT ); Thu, 9 Oct 2008 08:20:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756561AbYJIMT7 (ORCPT ); Thu, 9 Oct 2008 08:19:59 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:59604 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756356AbYJIMT7 (ORCPT ); Thu, 9 Oct 2008 08:19:59 -0400 Date: Thu, 9 Oct 2008 14:19:46 +0200 From: Ingo Molnar To: Cliff Wickman Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , "H. Peter Anvin" Subject: Re: [PATCH] UV: cosmetic fix to interrupt handler definition Message-ID: <20081009121946.GA1558@elte.hu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -0.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-0.5 required=5.9 tests=BAYES_20,DNS_FROM_SECURITYSAGE autolearn=no SpamAssassin version=3.2.3 -0.5 BAYES_20 BODY: Bayesian spam probability is 5 to 20% [score: 0.1281] 0.0 DNS_FROM_SECURITYSAGE RBL: Envelope sender in blackholes.securitysage.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 771 Lines: 24 * Cliff Wickman wrote: > From: Cliff Wickman > > The UV Broadcast Assist Unit (BAU) interrupt handler is erroneously > declared with a hardcoded vector 220 (that was used during testing). > It should be declared with the vector that is reserved for it. > > The interrupt handler does not use the 220 that is pushed onto its > stack, so this error had no runtime effect. > > Diffed against 2.6.27-rc8 > > Signed-off-by: Cliff Wickman applied to tip/x86/uv, thanks Cliff! Ingo -- 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/