From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<linux-hardening@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: ramoops: Inherit reserve memory property
Date: Mon, 30 Jan 2023 10:44:32 +0530 [thread overview]
Message-ID: <343d8b2f-9b7e-85ba-6f68-13cef73e55d0@quicinc.com> (raw)
In-Reply-To: <10097835-30fe-bbad-6c95-e5ec9dca3e2e@linaro.org>
On 1/28/2023 1:34 AM, Krzysztof Kozlowski wrote:
> On 27/01/2023 17:00, 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 inheriting some reserve memory
>> property to allocate the ramoops region dynamically.
>>
>> Cc: Kees Cook <keescook@chromium.org>
>> Cc: Tony Luck <tony.luck@intel.com>
>> Cc: Guilherme G. Piccoli <gpiccoli@igalia.com>
>> Cc: Rob Herring <robh+dt@kernel.org>
>> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
>
> Drop. There is no single need to store automated output of
> get_maintainers.pl in the git log forever. It can be easily re-created
> at any given time.
>
> If you need it for your own patch management purposes, keep it under ---.
>
Will drop, thanks.
> Additionally:
> where is patch number 2?
It was merged with 2/2 as it was not making sense to keep it as separate
patch
-Mukesh
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-01-30 5:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 16:00 Mukesh Ojha
2023-01-27 16:00 ` [PATCH v4 2/2] pstore/ram: Rework logic for detecting ramoops Mukesh Ojha
2023-01-27 19:18 ` [PATCH v4 1/2] dt-bindings: ramoops: Inherit reserve memory property Kees Cook
2023-01-27 20:03 ` Krzysztof Kozlowski
2023-01-30 8:13 ` Mukesh Ojha
2023-01-27 20:04 ` Krzysztof Kozlowski
2023-01-30 5:14 ` Mukesh Ojha [this message]
2023-01-27 20:05 ` Rob Herring
2023-01-30 8:32 ` Mukesh Ojha
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=343d8b2f-9b7e-85ba-6f68-13cef73e55d0@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®