From: Marc Zyngier <maz@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>, Peng Fan <peng.fan@nxp.com>,
Robin Murphy <robin.murphy@arm.com>,
Peter Geis <pgwipeout@gmail.com>,
XiaoDong Huang <derrick.huang@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v4 0/2] Add Rockchip RK3588 GIC ITS support
Date: Tue, 18 Apr 2023 17:35:04 +0100 [thread overview]
Message-ID: <864jpdkv2f.wl-maz@kernel.org> (raw)
In-Reply-To: <20230418142109.49762-1-sebastian.reichel@collabora.com>
On Tue, 18 Apr 2023 15:21:07 +0100,
Sebastian Reichel <sebastian.reichel@collabora.com> wrote:
>
> Hi,
>
> This adds GIC ITS support to Rockchip RK3588, which is affected
> by an integration issue effectively breaking shareability support.
> PCIe2 support will follow in its own series.
I've applied the first patch to irqchip-next. Please route the second
one via the SoC tree.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-04-18 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:21 [PATCH v4 0/2] Add Rockchip RK3588 GIC ITS support Sebastian Reichel
2023-04-18 14:21 ` [PATCH v4 1/2] irqchip/gic-v3: Add Rockchip 3588001 erratum workaround Sebastian Reichel
2023-04-18 14:21 ` [PATCH v4 2/2] arm64: dts: rockchip: rk3588: add GIC ITS support Sebastian Reichel
2023-04-18 16:35 ` Marc Zyngier [this message]
2023-04-19 15:56 ` (subset) [PATCH v4 0/2] Add Rockchip RK3588 " Heiko Stuebner
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=864jpdkv2f.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=derrick.huang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=peng.fan@nxp.com \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sebastian.reichel@collabora.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).