From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Varshini Rajendran <varshini.rajendran@microchip.com>,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@microchip.com,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 20/50] dt-bindings: atmel-nand: add microchip,sam9x7-pmecc
Date: Fri, 28 Jul 2023 12:06:35 +0100 [thread overview]
Message-ID: <b5c44fc5-005d-6268-af68-85eda9c330ba@linaro.org> (raw)
In-Reply-To: <20230728102636.266309-1-varshini.rajendran@microchip.com>
On 7/28/23 11:26, Varshini Rajendran wrote:
> Add microchip,sam9x7-pmecc to DT bindings documentation.
>
Why? What's the underlying problem that motivated you do this patch?
> Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com>
> ---
> Documentation/devicetree/bindings/mtd/atmel-nand.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/mtd/atmel-nand.txt b/Documentation/devicetree/bindings/mtd/atmel-nand.txt
> index 50645828ac20..4598930851d9 100644
> --- a/Documentation/devicetree/bindings/mtd/atmel-nand.txt
> +++ b/Documentation/devicetree/bindings/mtd/atmel-nand.txt
> @@ -56,6 +56,7 @@ Required properties:
> "atmel,sama5d4-pmecc"
> "atmel,sama5d2-pmecc"
> "microchip,sam9x60-pmecc"
> + "microchip,sam9x7-pmecc", "atmel,at91sam9g45-pmecc"
> - reg: should contain 2 register ranges. The first one is pointing to the PMECC
> block, and the second one to the PMECC_ERRLOC block.
>
next prev parent reply other threads:[~2023-07-28 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:26 [PATCH v3 20/50] dt-bindings: atmel-nand: add microchip,sam9x7-pmecc Varshini Rajendran
2023-07-28 11:06 ` Tudor Ambarus [this message]
2023-07-28 11:54 ` Krzysztof Kozlowski
2023-08-10 5:27 ` Varshini.Rajendran
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=b5c44fc5-005d-6268-af68-85eda9c330ba@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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=nicolas.ferre@microchip.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=varshini.rajendran@microchip.com \
--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).