From: "Jay Liu (刘博)" <Jay.Liu@mediatek.com>
To: "krzk@kernel.org" <krzk@kernel.org>
Cc: "linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"mripard@kernel.org" <mripard@kernel.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v4 0/6] porting pq compnent for MT8196
Date: Wed, 25 Mar 2026 13:26:42 +0000 [thread overview]
Message-ID: <62bd99417635c7c77f2e3fba77296ed3ac9aa603.camel@mediatek.com> (raw)
In-Reply-To: <20260325-hissing-jasmine-crayfish-caef70@quoll>
On Wed, 2026-03-25 at 09:17 +0100, Krzysztof Kozlowski wrote:
> On Tue, Mar 24, 2026 at 08:51:57PM +0800, Jay Liu wrote:
> > Change in v4:
> > - Address coding style comments for disp-tdshp binding.
>
> Coding style? Why so vague? So does that mean you ignored all
> important
> changes but did the "style" things?
>
> > - Rebase ccorr driver patch on top of latest linux-next to fix
> > conficts.
>
> Where is the rest of the changeglog?
>
> Why aren't you using b4 to provide also lore links and solve above
> problem?
>
> Best regards,
> Krzysztof
>
Dear Krzysztof,
I sincerely apologize for the confusion caused by my vague changelog.
My intention was to be concise, but I realize it made it look like I
ignored your technical feedback, which was not the case.
I have actually implemented the changes you requested in v3. Here is
the detailed breakdown of what was fixed in v4:
1. Sibling description: Removed as suggested.
2. Enum: Dropped the items list and used enum directly.
3. Formatting: Removed the extra blank line and fixed the indentation
in the example section.
Regarding the Node Name (disp-tdshp):
This was the only item I hesitated to change. "tdshp" stands for "2D
sharpness", and I kept it to align with MediaTek's internal naming.
However, I understand the upstream requirement for generic names. Since
this is a sharpness engine, would you prefer "sharpness-processor" or
something similar?
And Thank you for the recommendation regarding b4. I will set it up for
future submissions to ensure lore links and changelogs are generated
correctly.
I will send a v5 with a proper changelog and the node name update once
we agree on the name.
Please let me know if I missed any other comments or if you have
further suggestions. I will do my best to address them.
Best regards,
Jay
prev parent reply other threads:[~2026-03-25 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 12:51 Jay Liu
2026-03-24 12:51 ` [PATCH v4 1/6] dt-bindings: display: mediatek: gamma: Add support " Jay Liu
2026-03-24 12:51 ` [PATCH v4 2/6] dt-bindings: display: mediatek: dither: " Jay Liu
2026-03-24 12:52 ` [PATCH v4 3/6] dt-bindings: display: mediatek: ccorr: " Jay Liu
2026-03-24 12:52 ` [PATCH v4 4/6] dt-bindings: display: mediatek: disp-tdshp: " Jay Liu
2026-03-25 8:18 ` Krzysztof Kozlowski
2026-03-24 12:52 ` [PATCH v4 5/6] drm/mediatek: Support multiple CCORR component Jay Liu
2026-03-28 18:43 ` kernel test robot
2026-03-28 22:05 ` kernel test robot
2026-03-24 12:52 ` [PATCH v4 6/6] drm/mediatek: Add TDSHP component support for MT8196 Jay Liu
2026-03-28 20:08 ` kernel test robot
2026-03-25 8:17 ` [PATCH v4 0/6] porting pq compnent " Krzysztof Kozlowski
2026-03-25 13:26 ` Jay Liu (刘博) [this message]
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=62bd99417635c7c77f2e3fba77296ed3ac9aa603.camel@mediatek.com \
--to=jay.liu@mediatek.com \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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
all inboxes | Powered by JetHome®