From: Krzysztof Kozlowski <krzk@kernel.org>
To: Balamanikandan.Gunasundar@microchip.com,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
claudiu.beznea@tuxon.dev, krzysztof.kozlowski+dt@linaro.org
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] dt-bindings: mtd: atmel-nand: add legacy nand controllers
Date: Mon, 2 Jun 2025 11:17:07 +0200 [thread overview]
Message-ID: <34288beb-a00a-4b17-a893-87d569a440ef@kernel.org> (raw)
In-Reply-To: <e457c167-59d2-45c9-8da8-e9fbd1f5e17e@microchip.com>
On 02/06/2025 10:59, Balamanikandan.Gunasundar@microchip.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
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-06-02 9:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 5:35 [PATCH v3 0/4] dt-bindings: mtd: microchip-nand: convert txt to yaml Balamanikandan Gunasundar
2025-06-02 5:35 ` [PATCH v3 1/4] " Balamanikandan Gunasundar
2025-06-02 7:05 ` Rob Herring (Arm)
[not found] ` <654d2653-9152-449c-b3ee-4a91c700045e@microchip.com>
2025-06-02 12:42 ` Rob Herring
2025-06-02 5:35 ` [PATCH v3 2/4] dt-bindings: mtd: microchip-nand: add atmel pmecc Balamanikandan Gunasundar
2025-06-05 18:01 ` Rob Herring (Arm)
2025-06-02 5:35 ` [PATCH v3 3/4] dt-bindings: mtd: atmel-nand: add legacy nand controllers Balamanikandan Gunasundar
2025-06-02 7:23 ` Krzysztof Kozlowski
[not found] ` <e457c167-59d2-45c9-8da8-e9fbd1f5e17e@microchip.com>
2025-06-02 9:17 ` Krzysztof Kozlowski [this message]
2025-06-02 5:35 ` [PATCH v3 4/4] MAINTAINERS: add entry for microchip nand controller Balamanikandan Gunasundar
2025-06-02 7:17 ` Krzysztof Kozlowski
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=34288beb-a00a-4b17-a893-87d569a440ef@kernel.org \
--to=krzk@kernel.org \
--cc=Balamanikandan.Gunasundar@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh@kernel.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