From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753270AbbCIBl6 (ORCPT ); Sun, 8 Mar 2015 21:41:58 -0400 Received: from pmta1.delivery3.ore.mailhop.org ([54.191.214.36]:57227 "EHLO pmta1.delivery3.ore.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751891AbbCIBlz (ORCPT ); Sun, 8 Mar 2015 21:41:55 -0400 X-Greylist: delayed 97299 seconds by postgrey-1.27 at vger.kernel.org; Sun, 08 Mar 2015 21:41:55 EDT X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 72.84.113.125 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1/qZnkpFcIpO3dM3US8JkEiJ4mIBd14fHk= X-DKIM: OpenDKIM Filter v2.6.8 io 6665E80529 Date: Mon, 9 Mar 2015 01:22:53 +0000 From: Jason Cooper To: Stefan Agner Cc: tglx@linutronix.de, mark.rutland@arm.com, marc.zyngier@arm.com, u.kleine-koenig@pengutronix.de, shawn.guo@linaro.org, kernel@pengutronix.de, arnd@arndb.de, robh+dt@kernel.org, pawel.moll@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, pebolle@tiscali.nl, linux@arm.linux.org.uk, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v6 0/3] irqchip: vf610-mscm: add MSCM interrupt router driver Message-ID: <20150309012253.GI21207@io.lakedaemon.net> References: <1425249689-32354-1-git-send-email-stefan@agner.ch> <20150308053110.GF21207@io.lakedaemon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 09, 2015 at 12:43:56AM +0100, Stefan Agner wrote: > On 2015-03-08 06:31, Jason Cooper wrote: > > On Sun, Mar 01, 2015 at 11:41:26PM +0100, Stefan Agner wrote: > > ... > >> Stefan Agner (3): > >> irqchip: vf610-mscm-ir: add support for MSCM interrupt router > >> irqchip: vf610-mscm: dt-bindings: add MSCM bindings > >> ARM: dts: vf610: add Miscellaneous System Control Module (MSCM) > >> > >> .../arm/freescale/fsl,vf610-mscm-cpucfg.txt | 14 ++ > >> .../bindings/arm/freescale/fsl,vf610-mscm-ir.txt | 33 ++++ > >> arch/arm/boot/dts/vf500.dtsi | 137 +------------ > >> arch/arm/boot/dts/vfxxx.dtsi | 49 +++++ > >> arch/arm/mach-imx/Kconfig | 1 + > >> drivers/irqchip/Makefile | 1 + > >> drivers/irqchip/irq-vf610-mscm-ir.c | 212 +++++++++++++++++++++ > >> 7 files changed, 314 insertions(+), 133 deletions(-) > >> create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm-cpucfg.txt > >> create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,vf610-mscm-ir.txt > >> create mode 100644 drivers/irqchip/irq-vf610-mscm-ir.c > > > > Applied patches 1 and 2 to irqchip/vybrid. Please let me know if you need to > > base other work off of this. > > Thx. Some patches in the patchset to run Linux on the Cortex-M4 of > Vybrid is based on this driver. I will post a rebased version of that > probably tomorrow. What I meant, is: will you be submitting patches which have build or runtime dependencies on this branch? If so, I'll make sure to leave irqchip/vybrid up after I pull it into irqchip/core so that patches going into other trees and can depend on it. It's no extra work on my part, I just need to know not to clean it up ;-) thx, Jason.