From: Diederik de Haas <didi.debian@cknow.org>
To: liujianfeng1994@gmail.com, linux-rockchip@lists.infradead.org
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
ezequiel@vanguardiasur.com.ar, heiko@sntech.de,
jacob-chen@iotwrt.com, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-rockchip@lists.infradead.org, mchehab@kernel.org,
robh@kernel.org, sfr@canb.auug.org.au,
Jianfeng Liu <liujianfeng1994@gmail.com>,
Nicolas Dufresne <nicolas@ndufresne.ca>
Subject: Re: [PATCH v1 2/2] arm64: dts: rockchip: Add RGA2 support to rk3588
Date: Mon, 03 Jun 2024 17:50:23 +0200 [thread overview]
Message-ID: <1952296.0IMdUL435T@bagend> (raw)
In-Reply-To: <20240322064734.3509132-1-liujianfeng1994@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
Hi Jianfeng,
On Friday, 22 March 2024 07:47:34 CEST Jianfeng Liu wrote:
> This node is not sorted by bus-address, and anthoer patch adding hantro g1
> with addreess fdb50000 is not merged. I will send v2 after that patch is
> merged.
AFAICT the hantro g1 patch set is waiting on an answer to several questions
Nicolas raised, so maybe sent v2 of this patch set first?
Cheers,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-03 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 5:29 [PATCH v1 0/2] media: rockchip: rga: Add rk3568 support Jianfeng Liu
2024-03-22 5:29 ` [PATCH v1 1/2] dt-bindings: media: rockchip-rga: add rockchip,rk3588-rga Jianfeng Liu
2024-03-22 18:02 ` Conor Dooley
2024-03-22 5:29 ` [PATCH v1 2/2] arm64: dts: rockchip: Add RGA2 support to rk3588 Jianfeng Liu
2024-03-22 6:47 ` Jianfeng Liu
2024-06-03 15:50 ` Diederik de Haas [this message]
2024-03-22 5:42 ` [PATCH v1 0/2] media: rockchip: rga: Add rk3568 support Jianfeng Liu
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=1952296.0IMdUL435T@bagend \
--to=didi.debian@cknow.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=jacob-chen@iotwrt.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=liujianfeng1994@gmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).