[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0b255dd9-9922-497c-b3ff-9a850a1478fe@microchip.com>
Date: Mon, 2 Jun 2025 10:42:03 +0000
From: <Balamanikandan.Gunasundar@...rochip.com>
To: <krzk@...nel.org>, <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/25 2:47 pm, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> 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.
>
Sorry. I missed noticing the remaining part of the email. Not sure if it
is a problem with my email client. I will address the remaining
comments. Thanks for reviewing.
> Best regards,
> Krzysztof
Powered by blists - more mailing lists