[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150309012253.GI21207@io.lakedaemon.net>
Date: Mon, 9 Mar 2015 01:22:53 +0000
From: Jason Cooper <jason@...edaemon.net>
To: Stefan Agner <stefan@...er.ch>
Cc: tglx@...utronix.de, mark.rutland@....com, marc.zyngier@....com,
u.kleine-koenig@...gutronix.de, shawn.guo@...aro.org,
kernel@...gutronix.de, arnd@...db.de, robh+dt@...nel.org,
pawel.moll@....com, ijc+devicetree@...lion.org.uk,
galak@...eaurora.org, pebolle@...cali.nl, linux@....linux.org.uk,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 0/3] irqchip: vf610-mscm: add MSCM interrupt router
driver
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists