From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: Tinghan Shen <tinghan.shen@mediatek.com>,
	Chaotian Jing <chaotian.jing@mediatek.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Wenbin Mei <wenbin.mei@mediatek.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com,
	ryder.lee@kernel.org, wenst@chromium.org,
	chunfeng.yun@mediatek.com
Subject: Re: [PATCH v12 1/3] dt-bindings: mmc: mtk-sd: fix yamllint error
Date: Tue, 29 Mar 2022 14:47:50 +0200	[thread overview]
Message-ID: <97f2b11d-15c7-d28e-f7b5-e65f2f333580@collabora.com> (raw)
In-Reply-To: <20220329114540.17140-2-tinghan.shen@mediatek.com>
Il 29/03/22 13:45, Tinghan Shen ha scritto:
> Documentation/devicetree/bindings/mmc/mtk-sd.yaml
>    54:81     error    line too long (95 > 80 characters)  (line-length)
> 
I can't reproduce this error that you're getting... this commit is not
necessary, as the .yamllint file in the kernel allows a maximum line-length
of 110 characters.
rules:
   line-length:
     # 80 chars should be enough, but don't fail if a line is longer
     max: 110
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/.yamllint?h=next-20220329
Please drop this commit.
> Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com>
> ---
>   Documentation/devicetree/bindings/mmc/mtk-sd.yaml | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
next prev parent reply	other threads:[~2022-03-29 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 11:45 [PATCH v12 0/3] Add basic SoC support for mediatek mt8195 Tinghan Shen
2022-03-29 11:45 ` [PATCH v12 1/3] dt-bindings: mmc: mtk-sd: fix yamllint error Tinghan Shen
2022-03-29 12:47   ` AngeloGioacchino Del Regno [this message]
2022-03-30  2:55     ` Tinghan Shen
2022-03-29 11:45 ` [PATCH v12 2/3] dt-bindings: mmc: mtk-sd: increase reg maxItems Tinghan Shen
2022-03-29 12:43   ` AngeloGioacchino Del Regno
2022-03-29 19:10     ` Rob Herring
2022-03-30  8:20       ` AngeloGioacchino Del Regno
2022-03-29 14:27   ` Matthias Brugger
2022-03-30  7:33     ` Tinghan Shen
2022-03-29 20:38   ` Rob Herring
2022-03-30  7:25     ` Tinghan Shen
2022-03-29 11:45 ` [PATCH v12 3/3] arm64: dts: Add mediatek SoC mt8195 and evaluation board Tinghan Shen
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=97f2b11d-15c7-d28e-f7b5-e65f2f333580@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=chaotian.jing@mediatek.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=ryder.lee@kernel.org \
    --cc=tinghan.shen@mediatek.com \
    --cc=ulf.hansson@linaro.org \
    --cc=wenbin.mei@mediatek.com \
    --cc=wenst@chromium.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).