From: Rob Herring <robh@kernel.org>
To: David Heidelberg <david@ixit.cz>
Cc: Tony Luck <tony.luck@intel.com>,
Anton Vorontsov <anton@enomsg.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
~okias/devicetree@lists.sr.ht, Kees Cook <keescook@chromium.org>,
Colin Cross <ccross@android.com>
Subject: Re: [PATCH v3 4/4] dt-bindings: reserved-memory: ramoops: Convert txt bindings to yaml
Date: Mon, 18 Oct 2021 08:01:47 -0500 [thread overview]
Message-ID: <YW1wO+68XoJtoF19@robh.at.kernel.org> (raw)
In-Reply-To: <20211017141700.61201-4-david@ixit.cz>
On Sun, 17 Oct 2021 16:17:00 +0200, David Heidelberg wrote:
> Convert ramoops driver to the YAML syntax.
>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> v2:
> - inherit reserved-memory properties
> - switch to unevaluatedProperties
> v3:
> - add type references
> - enum -> oneOf
> - define maximum for max-reason
> - fixed max-reason node and remove accidentally created param: node
> - example: add root node
>
> .../bindings/reserved-memory/ramoops.txt | 66 --------
> .../bindings/reserved-memory/ramoops.yaml | 145 ++++++++++++++++++
> 2 files changed, 145 insertions(+), 66 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/reserved-memory/ramoops.txt
> create mode 100644 Documentation/devicetree/bindings/reserved-memory/ramoops.yaml
>
Applied, thanks!
prev parent reply other threads:[~2021-10-18 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 14:16 [PATCH v3 1/4] arm64: dts: qcom: SMxxxx: drop msg-size property from ramoops David Heidelberg
2021-10-17 14:16 ` [PATCH v3 2/4] arm64: dts: qcom: sm6350: fix typo in ecc-size property David Heidelberg
2021-10-17 14:16 ` [PATCH v3 3/4] arm64: dts: qcom: sm6350: remove compatible leftover from ramoops node David Heidelberg
2021-10-17 14:17 ` [PATCH v3 4/4] dt-bindings: reserved-memory: ramoops: Convert txt bindings to yaml David Heidelberg
2021-10-18 13:01 ` Rob Herring [this message]
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=YW1wO+68XoJtoF19@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony.luck@intel.com \
--cc=~okias/devicetree@lists.sr.ht \
/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).