From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Wed, 12 Apr 2017 23:14:42 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1]:59954 "EHLO linux-mips.org" rhost-flags-OK-OK-OK-FAIL) by eddie.linux-mips.org with ESMTP id S23993930AbdDLVOfU99NF (ORCPT ); Wed, 12 Apr 2017 23:14:35 +0200 Received: from h7.dl5rb.org.uk (localhost [127.0.0.1]) by h7.dl5rb.org.uk (8.15.2/8.14.8) with ESMTP id v3CLEWH4005826; Wed, 12 Apr 2017 23:14:33 +0200 Received: (from ralf@localhost) by h7.dl5rb.org.uk (8.15.2/8.15.2/Submit) id v3CLEV4U005825; Wed, 12 Apr 2017 23:14:32 +0200 Date: Wed, 12 Apr 2017 23:14:31 +0200 From: Ralf Baechle To: Thomas Gleixner Cc: Paul Burton , linux-mips@linux-mips.org, Marc Zyngier , Jason Cooper Subject: Re: [PATCH 0/5] MIPS/irqchip: Use IPI IRQ domains for CPU interrupt controller IPIs Message-ID: <20170412211431.GB31446@linux-mips.org> References: <20170330190614.14844-1-paul.burton@imgtec.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 57682 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ralf@linux-mips.org Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Fri, Mar 31, 2017 at 11:02:33AM +0200, Thomas Gleixner wrote: > On Thu, 30 Mar 2017, Paul Burton wrote: > > > This series introduces support for IPI IRQ domains to the CPU interrupt > > controller driver, allowing IPIs to function in the same way as those > > provided by the MIPS GIC as far as platform/board code is concerned. > > > > Doing this allows us to avoid duplicating code across platforms, avoid > > having to handle cases where IPI domains are or aren't in use depending > > upon the interrupt controller, and strengthen a sanity check for cases > > where IPI IRQ domains are supported. > > For the irqchip parts: > > Acked-by: Thomas Gleixner > > Ralf, feel free to route the whole lot through your MIPS tree. Done. Nice cleanup, Paul. Ralf