From: Rob Herring <robh@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: miquel.raynal@bootlin.com, linux-kernel@vger.kernel.org,
richard@nod.at, boris.brezillon@collabora.com,
linux-arm-msm@vger.kernel.org, Daniele.Palmas@telit.com,
vigneshr@ti.com, linux-mtd@lists.infradead.org,
bjorn.andersson@linaro.org, robh+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: mtd: Convert Qcom NANDc binding to YAML
Date: Sat, 6 Mar 2021 14:01:23 -0700 [thread overview]
Message-ID: <20210306210123.GA1206091@robh.at.kernel.org> (raw)
In-Reply-To: <20210225140842.66927-2-manivannan.sadhasivam@linaro.org>
On Thu, 25 Feb 2021 19:38:40 +0530, Manivannan Sadhasivam wrote:
> Convert Qcom NANDc devicetree binding to YAML.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> .../devicetree/bindings/mtd/qcom,nandc.yaml | 196 ++++++++++++++++++
> .../devicetree/bindings/mtd/qcom_nandc.txt | 142 -------------
> 2 files changed, 196 insertions(+), 142 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mtd/qcom,nandc.yaml
> delete mode 100644 Documentation/devicetree/bindings/mtd/qcom_nandc.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-03-06 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 14:08 [PATCH v3 0/3] Add support for secure regions in Qcom NANDc driver Manivannan Sadhasivam
2021-02-25 14:08 ` [PATCH v3 1/3] dt-bindings: mtd: Convert Qcom NANDc binding to YAML Manivannan Sadhasivam
2021-03-06 21:01 ` Rob Herring [this message]
2021-02-25 14:08 ` [PATCH v3 2/3] dt-bindings: mtd: Add a property to declare secure regions in NAND chips Manivannan Sadhasivam
2021-02-25 14:08 ` [PATCH v3 3/3] mtd: rawnand: qcom: Add support for secure regions in NAND memory Manivannan Sadhasivam
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=20210306210123.GA1206091@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Daniele.Palmas@telit.com \
--cc=bjorn.andersson@linaro.org \
--cc=boris.brezillon@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@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