From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Antoine Tenart <antoine.tenart@free-electrons.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
tglx@linutronix.de, jason@lakedaemon.net,
tsahee@annapurnalabs.com, rshitrit@annapurnalabs.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] irqchip: introduce the Alpine MSIX driver
Date: Thu, 11 Feb 2016 15:59:28 +0100 [thread overview]
Message-ID: <20160211155928.10695bb0@free-electrons.com> (raw)
In-Reply-To: <20160211144544.GC5820@kwain>
Hello,
On Thu, 11 Feb 2016 15:45:44 +0100, Antoine Tenart wrote:
> On Thu, Feb 11, 2016 at 01:41:48PM +0000, Marc Zyngier wrote:
> > On 10/02/16 13:22, Antoine Tenart wrote:
> > >
> > > This series introduce the Alpine MSIX driver, and enables it in both
> > > the Alpine v1 and Alpine v2 device trees.
> > >
> > > This series depends on "[PATCH v2 0/3] arm64: introduce the Alpine support":
> > > https://lkml.org/lkml/2016/2/10/83
> > >
> > > You can find the series at:
> > > https://github.com/atenart/linux.git 4.5-rc1/alpinev2-msix
> >
> > So I'm quite happy with this as it is (modulo the documentation fix on
> > patch 3). I can take the first 3 patches through my GIC tree, but the
> > last 4 patches depend on your other series.
>
> I'll fix the documentation.
>
> > Would it be a problem to get these 4 patches merged after 4.6-rc1, so
> > that all the code can be merged before?
>
> I think we can live with that :)
Practically speaking, patches 4-7 have no build dependency on patches
1-3, so they can be merged independently. As long as the DT binding
introduced in patches 1-3 is validated, then patches 4-7 can be merged
in parallel.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-02-11 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 13:22 [PATCH v2 0/7] irqchip: introduce the Alpine MSIX driver Antoine Tenart
2016-02-10 13:22 ` [PATCH v2 1/7] irqchip/gic-v3: always return IRQ_SET_MASK_OK_DONE in gic_set_affinity Antoine Tenart
2016-02-10 17:19 ` Marc Zyngier
2016-02-10 13:22 ` [PATCH v2 2/7] irqchip: add the Alpine MSIX interrupt controller Antoine Tenart
2016-02-11 13:27 ` Marc Zyngier
2016-02-10 13:22 ` [PATCH v2 3/7] Documentation: bindings: document the Alpine MSIX driver Antoine Tenart
2016-02-11 13:32 ` Marc Zyngier
2016-02-10 13:23 ` [PATCH v2 4/7] arm64: dts: alpine: add the MSIX node in the Alpine v2 dtsi Antoine Tenart
2016-02-10 13:23 ` [PATCH v2 5/7] ARM: dts: alpine: add the MSIX node Antoine Tenart
2016-02-10 13:23 ` [PATCH v2 6/7] arm64: alpine: select the Alpine MSI controller driver Antoine Tenart
2016-02-10 13:23 ` [PATCH v2 7/7] arm: " Antoine Tenart
2016-02-11 13:41 ` [PATCH v2 0/7] irqchip: introduce the Alpine MSIX driver Marc Zyngier
2016-02-11 14:45 ` Antoine Tenart
2016-02-11 14:59 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160211155928.10695bb0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rshitrit@annapurnalabs.com \
--cc=tglx@linutronix.de \
--cc=tsahee@annapurnalabs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox