From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>,
keescook@chromium.org, gpiccoli@igalia.com, corbet@lwn.net,
tony.luck@intel.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Cc: linux-hardening@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: reserved-memory: ramoops: Update the binding
Date: Fri, 27 Jan 2023 13:52:51 +0100 [thread overview]
Message-ID: <2958ec74-cc28-0bf4-36f8-19089487dd48@linaro.org> (raw)
In-Reply-To: <9610a38e-9f39-c514-f535-73434ae8f51a@quicinc.com>
On 27/01/2023 13:29, Mukesh Ojha wrote:
>>> +oneOf:
>>> + - required:
>>> + - reg
>>> +
>>> + - required:
>>> + - size
>>
>> There is no such property. You cannot require it.
>
> I was thinking, since this size is part reserved-memory.yaml and
> we have
>
> allOf:
> - $ref: "reserved-memory.yaml"
>
> Is your comment still applies?
Ah, you are right. It's ok.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-27 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 11:58 Mukesh Ojha
2023-01-13 11:58 ` [PATCH v2 2/3] Documentation: admin-guide: ramoops.rst: Update the ramoops document Mukesh Ojha
2023-01-13 13:24 ` Mukesh Ojha
2023-01-13 11:58 ` [PATCH v3 3/3] pstore/ram: Rework logic for detecting ramoops Mukesh Ojha
2023-01-13 12:04 ` [PATCH v2 1/3] dt-bindings: reserved-memory: ramoops: Update the binding Krzysztof Kozlowski
2023-01-13 13:22 ` Mukesh Ojha
2023-01-27 12:29 ` Mukesh Ojha
2023-01-27 12:52 ` Krzysztof Kozlowski [this message]
2023-01-13 15:26 ` 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=2958ec74-cc28-0bf4-36f8-19089487dd48@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®