From: <Balamanikandan.Gunasundar@microchip.com>
To: <krzk@kernel.org>, <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 4/4] MAINTAINERS: add entry for microchip nand controller
Date: Mon, 2 Jun 2025 08:56:44 +0000 [thread overview]
Message-ID: <50ec0069-2341-4ebb-a0a3-f503f0149fed@microchip.com> (raw)
In-Reply-To: <b17ff2df-aed1-42b0-9061-2f2e6655b958@kernel.org>
On 02/06/25 12: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 07:35, Balamanikandan Gunasundar wrote:
>> Add myself as maintainer for microchip nand controller driver
>>
>> Signed-off-by: Balamanikandan Gunasundar <balamanikandan.gunasundar@microchip.com>
>> ---
>> MAINTAINERS | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index dd844ac8d910..53cc327b8985 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -16064,9 +16064,10 @@ S: Maintained
>> F: drivers/mmc/host/atmel-mci.c
>>
>> MICROCHIP NAND DRIVER
>> +M: Balamanikandan Gunasundar <balamanikandan.gunasundar@microchip.com>
>> L: linux-mtd@lists.infradead.org
>> -S: Orphan
>> -F: Documentation/devicetree/bindings/mtd/atmel-nand.txt
>
> Your patchset is not bisectable. This belongs to the patch removing the
> file.
>
Yes. I will squash it appropriately and resend this.
>
> Best regards,
> Krzysztof
prev parent reply other threads:[~2025-06-02 8:56 UTC|newest]
Thread overview: 15+ 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 6:58 ` Balamanikandan.Gunasundar
2025-06-02 12:42 ` Rob Herring
2025-06-02 7:05 ` Rob Herring (Arm)
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
2025-06-02 8:59 ` Balamanikandan.Gunasundar
2025-06-02 9:17 ` Krzysztof Kozlowski
2025-06-02 10:42 ` Balamanikandan.Gunasundar
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
2025-06-02 8:56 ` Balamanikandan.Gunasundar [this message]
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=50ec0069-2341-4ebb-a0a3-f503f0149fed@microchip.com \
--to=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=krzk@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;
as well as URLs for NNTP newsgroup(s).