From: Stefan Wahren <stefan.wahren@i2se.com>
To: Rob Herring <robh+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>
Cc: Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Mwesigwa Guma <mguma@redhat.com>,
Ojaswin Mujoo <ojaswin98@gmail.com>,
Phil Elwell <phil@raspberrypi.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH 0/2] dt-bindings: soc: bcm: Convert brcm,bcm2835-vchiq to json-schemas
Date: Sun, 17 Oct 2021 15:06:34 +0200 [thread overview]
Message-ID: <1634475996-6809-1-git-send-email-stefan.wahren@i2se.com> (raw)
This series converts the VCHIQ bindings to YAML format.
Stefan Wahren (2):
ARM: dts: bcm283x: Drop fallback compatible for vchiq
dt-bindings: soc: bcm: Convert brcm,bcm2835-vchiq to json-schema
.../bindings/soc/bcm/brcm,bcm2835-vchiq.txt | 17 --------
.../bindings/soc/bcm/brcm,bcm2835-vchiq.yaml | 47 ++++++++++++++++++++++
arch/arm/boot/dts/bcm2836-rpi.dtsi | 2 +-
3 files changed, 48 insertions(+), 18 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt
create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.yaml
--
2.7.4
next reply other threads:[~2021-10-17 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 13:06 Stefan Wahren [this message]
2021-10-17 13:06 ` [PATCH 1/2] ARM: dts: bcm283x: Drop fallback compatible for vchiq Stefan Wahren
2021-10-17 13:06 ` [PATCH 2/2] dt-bindings: soc: bcm: Convert brcm,bcm2835-vchiq to json-schema Stefan Wahren
2021-10-17 15:29 ` Rob Herring
2021-10-17 16:31 ` [PATCH 2/2] dt-bindings: soc: bcm: Convert brcm, bcm2835-vchiq " Stefan Wahren
2021-10-18 12:44 ` Rob Herring
2021-10-26 23:30 ` [PATCH 2/2] dt-bindings: soc: bcm: Convert brcm,bcm2835-vchiq " 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=1634475996-6809-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=mguma@redhat.com \
--cc=nsaenz@kernel.org \
--cc=ojaswin98@gmail.com \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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).