From: Rob Herring <robh+dt@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Tanmay Shah <tanmay.shah@amd.com>,
andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org,
michal.simek@amd.com, bill.mills@linaro.org,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 0/6] Add Xilinx RPU subsystem support
Date: Sun, 20 Nov 2022 10:22:01 -0600 [thread overview]
Message-ID: <CAL_Jsq+ECUjFJHED9UnsgDrZQY_LUavDcQesZCwsnSH=iQCyrA@mail.gmail.com> (raw)
In-Reply-To: <20221116183814.GD61935@p14s>
On Wed, Nov 16, 2022 at 12:38 PM Mathieu Poirier
<mathieu.poirier@linaro.org> wrote:
>
> Hi Tanmay,
>
> I think this patchset is ready to be merged. Two things are missing though:
>
> Patches 1 and 2: We are missing a tag from one of the fellow in the DT brigade.
> They handle a lot of patches so let's give them time.
Patch 2 should go via the sub-arch tree. I don;t review .dts files regularly.
Rob
next prev parent reply other threads:[~2022-11-20 16:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 23:39 [PATCH v11 0/6] Add Xilinx RPU subsystem support Tanmay Shah
2022-11-14 23:39 ` [PATCH v11 1/6] dt-bindings: remoteproc: Add Xilinx RPU subsystem bindings Tanmay Shah
2022-11-20 16:18 ` Rob Herring
2022-11-14 23:39 ` [PATCH v11 2/6] arm64: dts: xilinx: zynqmp: Add RPU subsystem device node Tanmay Shah
2022-11-25 9:22 ` Michal Simek
2022-11-25 16:13 ` Mathieu Poirier
2022-11-14 23:39 ` [PATCH v11 3/6] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration Tanmay Shah
2022-11-14 23:39 ` [PATCH v11 4/6] firmware: xilinx: Add shutdown/wakeup APIs Tanmay Shah
2022-11-25 9:24 ` Michal Simek
2022-11-14 23:39 ` [PATCH v11 5/6] firmware: xilinx: Add RPU configuration APIs Tanmay Shah
2022-11-25 9:25 ` Michal Simek
2022-11-14 23:39 ` [PATCH v11 6/6] drivers: remoteproc: Add Xilinx r5 remoteproc driver Tanmay Shah
2022-11-16 18:38 ` [PATCH v11 0/6] Add Xilinx RPU subsystem support Mathieu Poirier
2022-11-16 20:46 ` Tanmay Shah
2022-11-20 16:22 ` Rob Herring [this message]
2022-11-20 16:26 ` Rob Herring
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='CAL_Jsq+ECUjFJHED9UnsgDrZQY_LUavDcQesZCwsnSH=iQCyrA@mail.gmail.com' \
--to=robh+dt@kernel.org \
--cc=andersson@kernel.org \
--cc=bill.mills@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@amd.com \
--cc=tanmay.shah@amd.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;
as well as URLs for NNTP newsgroup(s).