From: Krzysztof Kozlowski <krzk@kernel.org>
To: "CK Hu (胡俊光)" <ck.hu@mediatek.com>,
"robh@kernel.org" <robh@kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"Bo Kong (孔波)" <Bo.Kong@mediatek.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH v3 3/4] media: mediatek: add MT8188 AIE driver
Date: Tue, 31 Dec 2024 09:07:58 +0100 [thread overview]
Message-ID: <02618fb5-1ed4-44b4-943f-fe0f859d9fb6@kernel.org> (raw)
In-Reply-To: <b89b90b85e7c00889595bd8b8664d564ba8dc8ca.camel@mediatek.com>
On 31/12/2024 08:57, CK Hu (胡俊光) wrote:
>>>
>>> Why clear output buffer?
>>> Could you point out which place in the output buffer that hardware does not write data into but software would read it?
>>>
>> Please respond with one email doing review, not 10 per each comment.
>
> Sorry to bother you.
> I would try to respond in one email.
> Even though I have new comment when second review, I would not respond so frequently.
Second review? You sent 11 emails, so 11 reviews?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-31 8:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 9:00 [PATCH v3 0/4] Add AIE Driver bo.kong
2024-12-25 9:00 ` [PATCH v3 1/4] arm64: dts: mt8188: add aie node bo.kong
2024-12-25 9:00 ` [PATCH v3 2/4] media: dt-bindings: add MT8188 AIE bo.kong
2024-12-25 10:29 ` Rob Herring (Arm)
2024-12-25 11:28 ` Krzysztof Kozlowski
2024-12-26 3:41 ` CK Hu (胡俊光)
2024-12-25 9:00 ` [PATCH v3 4/4] uapi: linux: " bo.kong
2024-12-26 6:36 ` CK Hu (胡俊光)
2024-12-31 6:55 ` CK Hu (胡俊光)
[not found] ` <20241225090113.17027-4-bo.kong@mediatek.com>
2024-12-25 11:35 ` [PATCH v3 3/4] media: mediatek: add MT8188 AIE driver Krzysztof Kozlowski
2024-12-26 3:53 ` CK Hu (胡俊光)
2024-12-26 5:20 ` CK Hu (胡俊光)
2024-12-26 5:36 ` CK Hu (胡俊光)
2024-12-26 6:09 ` CK Hu (胡俊光)
2024-12-26 6:50 ` CK Hu (胡俊光)
2024-12-26 7:38 ` CK Hu (胡俊光)
2024-12-27 3:23 ` CK Hu (胡俊光)
2024-12-27 3:54 ` CK Hu (胡俊光)
2024-12-27 5:56 ` CK Hu (胡俊光)
2024-12-27 6:05 ` CK Hu (胡俊光)
2024-12-31 7:45 ` Krzysztof Kozlowski
2024-12-31 7:57 ` CK Hu (胡俊光)
2024-12-31 8:07 ` Krzysztof Kozlowski [this message]
2024-12-31 8:13 ` CK Hu (胡俊光)
2024-12-30 7:39 ` CK Hu (胡俊光)
2025-01-07 15:32 ` AngeloGioacchino Del Regno
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=02618fb5-1ed4-44b4-943f-fe0f859d9fb6@kernel.org \
--to=krzk@kernel.org \
--cc=Bo.Kong@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ck.hu@mediatek.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-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--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).