From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, <devicetree@vger.kernel.org>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <Tudor.Ambarus@microchip.com>,
juliensu@mxic.com.tw, Richard Weinberger <richard@nod.at>,
Boris Brezillon <boris.brezillon@collabora.com>,
linux-mtd@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
masonccyang@mxic.com.tw
Subject: [PATCH v12 0/2] NAND ECC engine binding changes
Date: Tue, 30 Jun 2020 09:28:20 +0200 [thread overview]
Message-ID: <20200630072822.26828-1-miquel.raynal@bootlin.com> (raw)
As part of a bigger series, I proposed these changes to facilitate the
insertion of a generic ECC engine abstraction, needed specifically for
new SPI-NAND devices not featuring any on-die engine.
The series is almost ready to be merged but the bindings did not pass
the checks. Now it is solved so I am just waiting for Rob's ack on
these two patches to apply the whole series.
Changes in v12:
* Actually send the corrected commits, ie. with a phandle type for the
ECC engine, a '|' to preserve the description formatting, boolean
types clearly defined for the two other properties and no more tabs.
Miquel Raynal (2):
dt-bindings: mtd: Document nand-ecc-engine
dt-bindings: mtd: Document boolean NAND ECC properties
.../bindings/mtd/nand-controller.yaml | 21 +++++++++++++++++++
1 file changed, 21 insertions(+)
--
2.20.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-06-30 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 7:28 Miquel Raynal [this message]
2020-06-30 7:28 ` [PATCH v12 1/2] dt-bindings: mtd: Document nand-ecc-engine Miquel Raynal
2020-07-09 20:02 ` Rob Herring
2020-06-30 7:28 ` [PATCH v12 2/2] dt-bindings: mtd: Document boolean NAND ECC properties Miquel Raynal
2020-07-09 20:03 ` Rob Herring
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=20200630072822.26828-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=boris.brezillon@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=juliensu@mxic.com.tw \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=masonccyang@mxic.com.tw \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).