devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Erez <erezgeva2@gmail.com>
Cc: Erez Geva <erezgeva@nwtime.org>,
	linux-mtd@lists.infradead.org,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Pratyush Yadav <pratyush@kernel.org>,
	Michael Walle <mwalle@kernel.org>,
	linux-kernel@vger.kernel.org,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Esben Haabendal <esben@geanix.com>
Subject: Re: [PATCH v4 3/5] dt-bindings: mtd: spi-nor: add OTP parameters
Date: Tue, 17 Sep 2024 19:32:16 +0200	[thread overview]
Message-ID: <fe98e49d-96d1-462f-99ac-93d8a53e55fd@kernel.org> (raw)
In-Reply-To: <CANeKEMNCFKX2thq+Ws0vy9ovbQ7dve3YPh_FbRaoOEgL+7c_Mw@mail.gmail.com>

On 17/09/2024 19:24, Erez wrote:
>>>>>>
>>>>>> It does not look like you tested the bindings, at least after quick
>>>>>> look. Please run `make dt_binding_check` (see
>>>>>
>>>>> I run "make dt_binding_check" on kernel 6.6.
>>>>
>>>> Yeah, we are no on kernel 6.6. You can run it also on kernel v4.1 -
>>>> still does not matter.
>>>>
>>>> Don't develop on ancient code because then you ask us to review same
>>>> broken stuff we already fixed.
>>>
>>> I test with Beaglebone black for testing, it is difficult to run the
>>> last vanille version.
>>> I did backport the spi-nor driver.
>>> As for "make dt_binding_check" on last kernel, it need to upgrade the tools,
>>>  and I did not think it could change that much.
>>>
>>
>> Well, it is possible to build kernel on small embedded board, but that's
>> quite cumbersone, slow and inefficient, considering that it's just
>> easier to cross compile. But anyway, binding check does not even need
>> cross compilation.
>>
>> Sorry, the code is obviously wrong, there is no such thing as u32, so
>> you did not test it. I provided link which explains how to test it. You
>> must do it on latest mainline kernel. Just like you must develop and
>> generate patches on latest mainline kernel, because this is where we
>> apply the patches. We do not apply them to v6.6.
> 
> The patches are based on the lastest  mainline kernel.
> I do not understand why you think otherwise.

Because you wrote:
"I run "make dt_binding_check" on kernel 6.6."

The command is either part of build process or final check process
(static analyzers etc). If you say you did this on v6.6, you got such
response.

Best regards,
Krzysztof


  reply	other threads:[~2024-09-17 17:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  9:49 [PATCH v4 0/5] Add support for SPI-NOR Macronix OTP Erez Geva
2024-09-17  9:49 ` [PATCH v4 1/5] mtd: spi-nor: core: add manufacturer flags Erez Geva
2024-09-17  9:49 ` [PATCH v4 2/5] mtd: spi-nor: core: add generic functions Erez Geva
2024-09-17  9:49 ` [PATCH v4 3/5] dt-bindings: mtd: spi-nor: add OTP parameters Erez Geva
2024-09-17 10:17   ` Erez
2024-09-17 10:35   ` Krzysztof Kozlowski
2024-09-17 10:42     ` Erez
2024-09-17 17:00       ` Krzysztof Kozlowski
2024-09-17 17:11         ` Erez
2024-09-17 17:17           ` Krzysztof Kozlowski
2024-09-17 17:24             ` Erez
2024-09-17 17:32               ` Krzysztof Kozlowski [this message]
2024-09-17 18:39                 ` Erez
2024-09-17 20:39                   ` Conor Dooley
2024-09-17 21:29                     ` Erez
2024-09-18  8:23                       ` Krzysztof Kozlowski
2024-09-18  9:46                         ` Erez
2024-09-17  9:49 ` [PATCH v4 4/5] mtd: spi-nor: macronix: add support for OTP Erez Geva
2024-09-17 10:32   ` Erez
2024-09-17  9:49 ` [PATCH v4 5/5] mtd: spi-nor: macronix: add manufacturer flags Erez Geva

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=fe98e49d-96d1-462f-99ac-93d8a53e55fd@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=erezgeva2@gmail.com \
    --cc=erezgeva@nwtime.org \
    --cc=esben@geanix.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=tudor.ambarus@linaro.org \
    --cc=vigneshr@ti.com \
    /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).