From: Dragan Cvetic <dragan.cvetic@amd.com>
To: <arnd@arndb.de>, <gregkh@linuxfoundation.org>,
<michal.simek@xilinx.com>, <linux-arm-kernel@lists.infradead.org>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<devicetree@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <git@amd.com>
Subject: [PATCH 0/2] dt-bindings: misc: xlnx,sd-fec: convert bindings to yaml
Date: Tue, 16 Jan 2024 11:11:33 +0000 [thread overview]
Message-ID: <20240116111135.3059-1-dragan.cvetic@amd.com> (raw)
This patchset converts AMD (Xilinx) sd-fec bindings to yaml format,
so it can validate dt-entries as well as any future additions to yaml.
Conversion txt to yamal is done "one to one", no new changes has been made
in DT binding file.
Convert sd-fec DT binding file extension from .txt to .yaml in
the MAINTAINERS file
Dragan Cvetic (2):
dt-bindings: misc: xlnx,sd-fec: convert bindings to yaml
MAINTAINERS: Update sd-fec documentation file from txt to yaml
.../devicetree/bindings/misc/xlnx,sd-fec.txt | 58 --------
.../devicetree/bindings/misc/xlnx,sd-fec.yaml | 132 ++++++++++++++++++
MAINTAINERS | 2 +-
3 files changed, 133 insertions(+), 59 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/misc/xlnx,sd-fec.txt
create mode 100644 Documentation/devicetree/bindings/misc/xlnx,sd-fec.yaml
--
2.17.1
next reply other threads:[~2024-01-16 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 11:11 Dragan Cvetic [this message]
2024-01-16 11:11 ` [PATCH 1/2] " Dragan Cvetic
2024-01-16 15:20 ` Krzysztof Kozlowski
2024-01-16 15:36 ` Michal Simek
2024-01-16 15:44 ` Krzysztof Kozlowski
2024-01-18 1:07 ` Cvetic, Dragan
2024-01-18 0:49 ` Cvetic, Dragan
2024-01-19 17:58 ` kernel test robot
2024-01-16 11:11 ` [PATCH 2/2] MAINTAINERS: Update sd-fec documentation file from txt " Dragan Cvetic
2024-01-16 15:13 ` Krzysztof Kozlowski
2024-01-18 9:23 ` Cvetic, Dragan
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=20240116111135.3059-1-dragan.cvetic@amd.com \
--to=dragan.cvetic@amd.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®