From: Rob Herring <robh@kernel.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: linux-hardening@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
keescook@chromium.org, tony.luck@intel.com, gpiccoli@igalia.com,
krzysztof.kozlowski+dt@linaro.org, corbet@lwn.net
Subject: Re: [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the region dynamically
Date: Thu, 2 Feb 2023 17:59:16 -0600 [thread overview]
Message-ID: <20230202235916.GA2931100-robh@kernel.org> (raw)
In-Reply-To: <1675330081-15029-1-git-send-email-quic_mojha@quicinc.com>
On Thu, Feb 02, 2023 at 02:58:00PM +0530, Mukesh Ojha wrote:
> The reserved memory region for ramoops is assumed to be at a
> fixed and known location when read from the devicetree. This
> is not desirable in an environment where it is preferred the
> region to be dynamically allocated at runtime, as opposed to
> being fixed at compile time.
>
> So, update the ramoops binding by using some reserve memory
> property to allocate the ramoops region dynamically.
Sorry, but I still don't think this belongs in DT as I commented on v4.
next prev parent reply other threads:[~2023-02-02 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 9:28 [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the region dynamically Mukesh Ojha
2023-02-02 9:28 ` [PATCH v5 2/2] pstore/ram: Rework logic for detecting ramoops Mukesh Ojha
2023-02-14 13:44 ` Mukesh Ojha
2023-02-02 23:59 ` Rob Herring [this message]
2023-02-03 8:20 ` [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the region dynamically Mukesh Ojha
2023-02-03 14:59 ` 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=20230202235916.GA2931100-robh@kernel.org \
--to=robh@kernel.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=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;
as well as URLs for NNTP newsgroup(s).