From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Xiangzhi Tang (唐相志)" <Xiangzhi.Tang@mediatek.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"andersson@kernel.org" <andersson@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Hailong Fan (范海龙)" <Hailong.Fan@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Jjian Zhou (周建)" <Jjian.Zhou@mediatek.com>
Subject: Re: [PATCH 1/2] dt-bindings: remoteproc: Add VCP support for mt8196
Date: Sun, 6 Apr 2025 14:10:17 +0200 [thread overview]
Message-ID: <21095cf1-45b2-4c41-933a-a0a4afc2cabb@kernel.org> (raw)
In-Reply-To: <625410299fd45188759d3b1fe205e6c42af0bbda.camel@mediatek.com>
On 06/04/2025 08:46, Xiangzhi Tang (唐相志) wrote:
> On Wed, 2025-04-02 at 13:11 +0200, Krzysztof Kozlowski wrote:
>> External email : Please do not click links or open attachments until
>> you have verified the sender or the content.
>>
>>
>> On 02/04/2025 11:19, Xiangzhi Tang wrote:
>>> +
>>> +description:
>>> + The MediaTek VCP enables the SoC control the MediaTek Video
>>> Companion Risc-V coprocessor.
>>
>> Wrap at coding style.
>> Thanks comment, I will fix it on v1 version.
>>
Please kindly trim the replies from unnecessary context. It makes it
much easier to find new content.
Anyway, not sure what you are referring to, but this was not fully
tested and I still expect all my comments to be addressed.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-06 12:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 9:19 [PATCH 0/2] Add vcp driver Xiangzhi Tang
2025-04-02 9:19 ` [PATCH 1/2] dt-bindings: remoteproc: Add VCP support for mt8196 Xiangzhi Tang
2025-04-02 11:11 ` Krzysztof Kozlowski
2025-04-06 6:46 ` Xiangzhi Tang (唐相志)
2025-04-06 12:10 ` Krzysztof Kozlowski [this message]
2025-04-02 12:55 ` Rob Herring (Arm)
2025-04-06 8:04 ` Xiangzhi Tang (唐相志)
2025-04-02 9:19 ` [PATCH 2/2] remoterpoc: mediatek: vcp: Add vcp remoteproc driver Xiangzhi Tang
2025-04-02 11:16 ` Krzysztof Kozlowski
2025-04-06 7:29 ` Xiangzhi Tang (唐相志)
2025-04-06 12:12 ` Krzysztof Kozlowski
2025-04-02 14:19 ` Mathieu Poirier
2025-04-02 10:31 ` [PATCH 0/2] Add vcp driver Krzysztof Kozlowski
2025-04-06 8:05 ` Xiangzhi Tang (唐相志)
2025-04-06 12:13 ` Krzysztof Kozlowski
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=21095cf1-45b2-4c41-933a-a0a4afc2cabb@kernel.org \
--to=krzk@kernel.org \
--cc=Hailong.Fan@mediatek.com \
--cc=Jjian.Zhou@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Xiangzhi.Tang@mediatek.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.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 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).