From: Vignesh Raghavendra <vigneshr@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Rob Herring <robh+dt@kernel.org>, <linux-mtd@lists.infradead.org>,
<devicetree@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] mtd: Convert hyperflash/hyperbus bindings to YAML schema
Date: Fri, 11 Jun 2021 11:05:31 +0530 [thread overview]
Message-ID: <20210611053533.16701-1-vigneshr@ti.com> (raw)
This series converts Cypress hyperflash and TI AM654 HyperBus Controller
bindings to YAML schema.
Vignesh Raghavendra (2):
dt-bindings: mtd: Convert cypress,hyperflash to YAML schema
dt-bindings: mtd: Convert ti,am654-hbmc.txt to YAML schema
.../bindings/mtd/cypress,hyperflash.yaml | 51 ++++++++++++++
.../devicetree/bindings/mtd/ti,am654-hbmc.txt | 51 --------------
.../bindings/mtd/ti,am654-hbmc.yaml | 69 +++++++++++++++++++
3 files changed, 120 insertions(+), 51 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mtd/cypress,hyperflash.yaml
delete mode 100644 Documentation/devicetree/bindings/mtd/ti,am654-hbmc.txt
create mode 100644 Documentation/devicetree/bindings/mtd/ti,am654-hbmc.yaml
--
2.32.0
WARNING: multiple messages have this Message-ID (diff)
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Rob Herring <robh+dt@kernel.org>, <linux-mtd@lists.infradead.org>,
<devicetree@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] mtd: Convert hyperflash/hyperbus bindings to YAML schema
Date: Fri, 11 Jun 2021 11:05:31 +0530 [thread overview]
Message-ID: <20210611053533.16701-1-vigneshr@ti.com> (raw)
This series converts Cypress hyperflash and TI AM654 HyperBus Controller
bindings to YAML schema.
Vignesh Raghavendra (2):
dt-bindings: mtd: Convert cypress,hyperflash to YAML schema
dt-bindings: mtd: Convert ti,am654-hbmc.txt to YAML schema
.../bindings/mtd/cypress,hyperflash.yaml | 51 ++++++++++++++
.../devicetree/bindings/mtd/ti,am654-hbmc.txt | 51 --------------
.../bindings/mtd/ti,am654-hbmc.yaml | 69 +++++++++++++++++++
3 files changed, 120 insertions(+), 51 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mtd/cypress,hyperflash.yaml
delete mode 100644 Documentation/devicetree/bindings/mtd/ti,am654-hbmc.txt
create mode 100644 Documentation/devicetree/bindings/mtd/ti,am654-hbmc.yaml
--
2.32.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Rob Herring <robh+dt@kernel.org>, <linux-mtd@lists.infradead.org>,
<devicetree@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] mtd: Convert hyperflash/hyperbus bindings to YAML schema
Date: Fri, 11 Jun 2021 11:05:31 +0530 [thread overview]
Message-ID: <20210611053533.16701-1-vigneshr@ti.com> (raw)
This series converts Cypress hyperflash and TI AM654 HyperBus Controller
bindings to YAML schema.
Vignesh Raghavendra (2):
dt-bindings: mtd: Convert cypress,hyperflash to YAML schema
dt-bindings: mtd: Convert ti,am654-hbmc.txt to YAML schema
.../bindings/mtd/cypress,hyperflash.yaml | 51 ++++++++++++++
.../devicetree/bindings/mtd/ti,am654-hbmc.txt | 51 --------------
.../bindings/mtd/ti,am654-hbmc.yaml | 69 +++++++++++++++++++
3 files changed, 120 insertions(+), 51 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mtd/cypress,hyperflash.yaml
delete mode 100644 Documentation/devicetree/bindings/mtd/ti,am654-hbmc.txt
create mode 100644 Documentation/devicetree/bindings/mtd/ti,am654-hbmc.yaml
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-06-11 5:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 5:35 Vignesh Raghavendra [this message]
2021-06-11 5:35 ` [PATCH 0/2] mtd: Convert hyperflash/hyperbus bindings to YAML schema Vignesh Raghavendra
2021-06-11 5:35 ` Vignesh Raghavendra
2021-06-11 5:35 ` [PATCH 1/2] dt-bindings: mtd: Convert cypress,hyperflash " Vignesh Raghavendra
2021-06-11 5:35 ` [PATCH 1/2] dt-bindings: mtd: Convert cypress, hyperflash " Vignesh Raghavendra
2021-06-11 5:35 ` Vignesh Raghavendra
2021-06-11 15:10 ` [PATCH 1/2] dt-bindings: mtd: Convert cypress,hyperflash " Rob Herring
2021-06-11 15:10 ` [PATCH 1/2] dt-bindings: mtd: Convert cypress, hyperflash " Rob Herring
2021-06-11 15:10 ` Rob Herring
2021-06-11 5:35 ` [PATCH 2/2] dt-bindings: mtd: Convert ti,am654-hbmc.txt " Vignesh Raghavendra
2021-06-11 5:35 ` [PATCH 2/2] dt-bindings: mtd: Convert ti, am654-hbmc.txt " Vignesh Raghavendra
2021-06-11 5:35 ` Vignesh Raghavendra
2021-06-11 17:48 ` [PATCH 2/2] dt-bindings: mtd: Convert ti,am654-hbmc.txt " Rob Herring
2021-06-11 17:48 ` Rob Herring
2021-06-11 17:48 ` 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=20210611053533.16701-1-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.