From: <Hermes.Wu@ite.com.tw>
To: <krzk@kernel.org>
Cc: <andrzej.hajda@intel.com>, <neil.armstrong@linaro.org>,
<rfoss@kernel.org>, <Laurent.pinchart@ideasonboard.com>,
<jonas@kwiboo.se>, <jernej.skrabec@gmail.com>,
<airlied@gmail.com>, <simona@ffwll.ch>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <luca.ceresoli@bootlin.com>,
<Pet.Weng@ite.com.tw>, <Kenneth.Hung@ite.com.tw>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<dmitry.baryshkov@oss.qualcomm.com>
Subject: RE: [PATCH v5 1/2] dt-bindings: display: bridge: Add ITE IT6162 MIPI DSI to HDMI bridge
Date: Mon, 2 Nov 2026 02:04:20 +0000 [thread overview]
Message-ID: <6af49c44a6bb477f8038266d3621bfab@ite.com.tw> (raw)
In-Reply-To: <182ebaf9-0e6c-413a-971a-396ee8cd6b5b@kernel.org>
Hi Krzysztof
On 30/10/2026 11:49, Krzysztof Kozlowski wrote:
> On 30/10/2026 11:44, Hermes.Wu@ite.com.tw wrote:
>> I ran checkpatch.pl, with and without --strict, on both patches. The
>
> I don't believe in such case that you run on any valid kernel tree.
>
> Please fix your workflow, because it seems you work on some ancient
> tree (don't, instead use mainline) or work on fork of kernel (don't,
> instead use mainline).
Sorry, my mistake.
I ran checkpatch.pl from the drm-misc tree's drm-misc-next branch, which the series is based on.
That tree does not have commit 1e035297ffda ("docs: remove Assisted-by references") yet, so its checkpatch.pl still accepts the Assisted-by tag.
With checkpatch.pl from mainline I can see the warnings now. I will drop the tag in v6 and check the patches with checkpatch.pl from mainline before sending.
One question so I get v6 right: should I keep basing the series on drm-misc-next, since the bridge patches go through drm-misc, and only
use mainline for checkpatch.pl and the other tools? Or would you prefer the series to be based on mainline?
Thanks,
Hermes
next prev parent reply other threads:[~2026-11-02 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 10:12 [PATCH v5 0/2] Add ITE IT6162 MIPI DSI to HDMI bridge driver Hermes Wu via B4 Relay
2026-10-29 10:12 ` [PATCH v5 1/2] dt-bindings: display: bridge: Add ITE IT6162 MIPI DSI to HDMI bridge Hermes Wu via B4 Relay
2026-10-30 9:56 ` Krzysztof Kozlowski
2026-10-30 10:44 ` Hermes.Wu
2026-10-30 10:49 ` Krzysztof Kozlowski
2026-11-02 2:04 ` Hermes.Wu [this message]
2026-10-29 10:12 ` [PATCH v5 2/2] drm/bridge: Add ITE IT6162 MIPI DSI to HDMI bridge driver Hermes Wu via B4 Relay
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=6af49c44a6bb477f8038266d3621bfab@ite.com.tw \
--to=hermes.wu@ite.com.tw \
--cc=Kenneth.Hung@ite.com.tw \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Pet.Weng@ite.com.tw \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--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®