public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Animesh Agarwal <animeshagarwal28@gmail.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-ide@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] dt-bindings: imx-pata: Convert to dtschema
Date: Tue, 12 Mar 2024 17:25:45 +0100	[thread overview]
Message-ID: <045ae9cf-104d-472e-94f0-ea7cd5298214@linaro.org> (raw)
In-Reply-To: <20240311140435.34329-1-animeshagarwal28@gmail.com>

On 11/03/2024 15:04, Animesh Agarwal wrote:
> Convert the imx-pata bindings to DT schema.
> Add missing fsl,imx31-pata and
> fsl,imx51-pata compatibles during conversion,
> because they are already being used in existing DTS.

Thank you for improving the commit msg. It looks a bit oddly wrapped. In
the future, please wrap commit message according to Linux coding style /
submission process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597

No need to resend just for this... but...
> 
> Signed-off-by: Animesh Agarwal <animeshagarwal28@gmail.com>
> 
> ---
> Changes in v7:
> - removed blank space at the end of file.
> 


> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    pata: pata@83fe0000 {
> +        compatible = "fsl,imx51-pata","fsl,imx27-pata";

Oh my... missing space after coma, but more important: what is happening
here? The space was here before in previous versions, so you removed it!
At least till v4 it was correct and bam - now it is not. Why? It's the
same confusing as new line appearing suddenly in v6.

It looks like between each revisions of patchset some random changes
appear in your code. How is it possible? Don't you work with Git? You
change file, git add -p and git commit --amend. Why unrelated changes
keep happening?

While the actual space is a nitpick, it points to the fact that your
patch experiences some changes in an unexpected way and we cannot trust
that you did only what you claim in changelog.

Best regards,
Krzysztof


  reply	other threads:[~2024-03-12 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 14:04 [PATCH v7] dt-bindings: imx-pata: Convert to dtschema Animesh Agarwal
2024-03-12 16:25 ` Krzysztof Kozlowski [this message]
2024-03-12 16:49   ` Animesh Agarwal

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=045ae9cf-104d-472e-94f0-ea7cd5298214@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=animeshagarwal28@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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