From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 7B897DDEC5 for ; Tue, 24 Apr 2007 03:34:20 +1000 (EST) In-Reply-To: <1177317115.3889.39.camel@concordia.ozlabs.ibm.com> References: <20070419073556.73A6BDDE4A@ozlabs.org> <20070422193017.GA27048@lixom.net> <829d8b36a3c78c662f29437c59290609@kernel.crashing.org> <1177317115.3889.39.camel@concordia.ozlabs.ibm.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <7928ad59f5dd4429dcb0c22792c210f7@kernel.crashing.org> From: Segher Boessenkool Subject: Re: [PATCH 7/7] MPIC MSI backend Date: Mon, 23 Apr 2007 19:33:54 +0200 To: michael@ellerman.id.au Cc: Olof Johansson , linuxppc-dev@ozlabs.org, linux-pci , Milton Miller List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >>>> mpic_htmsi deals with MSIs that come in over hypertransport >>>> to the MPIC on CPC925/CPC945; this has nothing to >>>> do with HT APICs. >>> >>> Maybe it should be named mpic_cpc9x5msi instead? >> >> Yeah probably, esp. since there are more MSI sources >> on those chips, not just HT; and if support for those >> sources gets added later, it should go to this file :-) > > Actually I think I'll call it mpic_u3_msi.c, which although not quite > as > accurate as cpc9x5, is more inline with the rest of the code that > refers > to U3 - which really means U3/U4. Yeah, good plan. It's a nicer name anyway :-) Segher