From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] irqchip: introduce the Alpine MSIX driver
Date: Thu, 11 Feb 2016 13:41:48 +0000 [thread overview]
Message-ID: <56BC8F9C.3060505@arm.com> (raw)
In-Reply-To: <1455110583-19515-1-git-send-email-antoine.tenart@free-electrons.com>
Antoine,
On 10/02/16 13:22, Antoine Tenart wrote:
> Hi all,
>
> 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.
Would it be a problem to get these 4 patches merged after 4.6-rc1, so
that all the code can be merged before?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Antoine Tenart <antoine.tenart@free-electrons.com>,
tglx@linutronix.de, jason@lakedaemon.net,
tsahee@annapurnalabs.com
Cc: rshitrit@annapurnalabs.com, thomas.petazzoni@free-electrons.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 13:41:48 +0000 [thread overview]
Message-ID: <56BC8F9C.3060505@arm.com> (raw)
In-Reply-To: <1455110583-19515-1-git-send-email-antoine.tenart@free-electrons.com>
Antoine,
On 10/02/16 13:22, Antoine Tenart wrote:
> Hi all,
>
> 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.
Would it be a problem to get these 4 patches merged after 4.6-rc1, so
that all the code can be merged before?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-02-11 13:41 UTC|newest]
Thread overview: 28+ 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 ` 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 13:22 ` Antoine Tenart
2016-02-10 17:19 ` Marc Zyngier
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-10 13:22 ` Antoine Tenart
2016-02-11 13:27 ` Marc Zyngier
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-10 13:22 ` Antoine Tenart
2016-02-11 13:32 ` Marc Zyngier
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 ` 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 ` 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 ` Antoine Tenart
2016-02-10 13:23 ` [PATCH v2 7/7] arm: " Antoine Tenart
2016-02-10 13:23 ` Antoine Tenart
2016-02-11 13:41 ` Marc Zyngier [this message]
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:45 ` Antoine Tenart
2016-02-11 14:59 ` Thomas Petazzoni
2016-02-11 14:59 ` Thomas Petazzoni
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=56BC8F9C.3060505@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.