From: Krzysztof Kozlowski <krzk@kernel.org>
To: Liankun Yang <liankun.yang@mediatek.com>,
chunkuang.hu@kernel.org, p.zabel@pengutronix.de,
airlied@gmail.com, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
chunfeng.yun@mediatek.com, vkoul@kernel.org, kishon@kernel.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
jitao.shi@mediatek.com, mac.shen@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com
Cc: dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH v2 2/2] Add dp PHY dt-bindings
Date: Mon, 13 May 2024 08:37:29 +0200 [thread overview]
Message-ID: <e02c2f42-b5e4-4200-8131-3881b7034625@kernel.org> (raw)
In-Reply-To: <20240510110523.12524-3-liankun.yang@mediatek.com>
On 10/05/2024 13:04, Liankun Yang wrote:
> Add dp PHY dt-bindings.
This tells me nothing. Read submitting patches.
>
> Changeds in v2:
This does goes to changelog, not commit log.
> - Add dp PHY dt-bindings.
> https://patchwork.kernel.org/project/linux-mediatek/patch/
> 20240403040517.3279-1-liankun.yang@mediatek.com/
>
> Signed-off-by: Liankun Yang <liankun.yang@mediatek.com>
This patch looks terrible... there's so many wrong things I don't even
know where to start.
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
Please run scripts/checkpatch.pl and fix reported warnings. Then please
run `scripts/checkpatch.pl --strict` and (probably) fix more warnings.
Some warnings can be ignored, especially from --strict run, but the code
here looks like it needs a fix. Feel free to get in touch if the warning
is not clear.
> ---
> .../display/mediatek/mediatek.phy-dp.yaml | 45 +++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek.phy-dp.yaml
Wrong filename
>
> diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek.phy-dp.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek.phy-dp.yaml
> index 000000000000..476bc329363f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek.phy-dp.yaml
> @@ -0,0 +1,45 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/mediatek/mediatek,phy-dp.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MediaTek Display Port Controller
> +
> +maintainers:
> + - Mac shen <mac.shen@mediatek.com>
> + - Liankun yang <Liankun.yang@mediatek.com>
> +
> +description: |
> + Special settings need to be configured by MediaTek DP based on the actual
> + hardware situation. For example, when using a certain brand's docking
> + station for display projection, garbage may appear. Adjusting the specific
> + ssc value can resolve this issue.
> +
> +properties:
> + status: disabled
I think you nicely shocked Rob already.
Please reach internally to Mediatek or collaborating companies to get
basic training and instructions how to write patches and bindings.
Otherwise it is waste of our time. Mediatek is not a small company so
there is no excuse in sending such poor quality patches, which would be
EASILY spotted by the MOST BASIC review.
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-05-13 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 11:04 [PATCH v2 0/2] Add PHY-dp bindings Liankun Yang
2024-05-10 11:04 ` [PATCH v2 1/2] Add write DP phyd register from parse dts Liankun Yang
2024-05-13 6:38 ` Krzysztof Kozlowski
2024-05-13 14:21 ` LIANKUN YANG (杨连坤)
2024-05-13 13:11 ` AngeloGioacchino Del Regno
2024-05-13 14:26 ` LIANKUN YANG (杨连坤)
2024-05-10 11:04 ` [PATCH v2 2/2] Add dp PHY dt-bindings Liankun Yang
2024-05-10 12:48 ` Rob Herring
2024-05-13 14:06 ` LIANKUN YANG (杨连坤)
2024-05-13 6:37 ` Krzysztof Kozlowski [this message]
2024-05-13 14:15 ` LIANKUN YANG (杨连坤)
2024-05-13 14:17 ` Krzysztof Kozlowski
2024-05-13 14:20 ` Krzysztof Kozlowski
2024-05-14 4:43 ` LIANKUN YANG (杨连坤)
2024-05-10 11:27 ` [PATCH v2 0/2] Add PHY-dp bindings Jani Nikula
2024-05-13 13:57 ` LIANKUN YANG (杨连坤)
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=e02c2f42-b5e4-4200-8131-3881b7034625@kernel.org \
--to=krzk@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jitao.shi@mediatek.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=liankun.yang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mac.shen@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=tzimmermann@suse.de \
--cc=vkoul@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