[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <34288beb-a00a-4b17-a893-87d569a440ef@kernel.org>
Date: Mon, 2 Jun 2025 11:17:07 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Balamanikandan.Gunasundar@...rochip.com, miquel.raynal@...tlin.com,
richard@....at, vigneshr@...com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, Nicolas.Ferre@...rochip.com,
alexandre.belloni@...tlin.com, claudiu.beznea@...on.dev,
krzysztof.kozlowski+dt@...aro.org
Cc: linux-mtd@...ts.infradead.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/4] dt-bindings: mtd: atmel-nand: add legacy nand
controllers
On 02/06/2025 10:59, Balamanikandan.Gunasundar@...rochip.com wrote:
> On 02/06/25 12:53 pm, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On 02/06/2025 07:35, Balamanikandan Gunasundar wrote:
>>> Add support for atmel legacy nand controllers. These bindings should not be
>>
>> No new support for legacy bindings. Both your commit msg and subject do
>> not describe what you do here. I see you convert EXISTING bindings
>> instead of adding support. But if you insist on adding, that would be
>> NAKed because why would we want to accept new stuff which is already
>> deprecated?
>
> Yes. I am just converting the exiting bindings. Hope rephrasing the
> commit message is sufficient enough.
And you just ignored everything else? Please kindly trim the replies
from unnecessary context. It makes it much easier to find new content.
Best regards,
Krzysztof
Powered by blists - more mailing lists