From: Krzysztof Kozlowski <krzk@kernel.org>
To: Abhishek Tiwari <abhitiwari@linux.microsoft.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
kees@kernel.org, tony.luck@intel.com, gpiccoli@igalia.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Cc: abhitiwari@microsoft.com
Subject: Re: [PATCH] dt-bindings: memory: Document linux,usable-memory property
Date: Thu, 13 Mar 2025 17:10:23 +0100 [thread overview]
Message-ID: <9c52990b-c8fd-440f-bd2c-bfa0e63c00fc@kernel.org> (raw)
In-Reply-To: <1741874545-19091-1-git-send-email-abhitiwari@linux.microsoft.com>
On 13/03/2025 15:02, Abhishek Tiwari wrote:
> Add Documentation for linux,usable-memory
>
> Signed-off-by: Abhishek Tiwari <abhitiwari@linux.microsoft.com>
> ---
> .../bindings/linux,usable-memory.txt | 32 +++++++++++++++++++
No TXT bindings anymore.
But anyway, please explain why reserved memory and the standard memory
node are not sufficient for you. For example:
> +
> +Common use cases include:
> +- Allocating ``ramoops`` region
this is reserved memory.
> +- Reserving memory for hardware-specific needs
Same.
> +- Fake Protecting persistent memory (PMEM)
Same.
What's more, explain why linux,usable-memory-range is not good... or you
just send some old patch from downstream forks?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-13 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 14:02 [PATCH] dt-bindings: memory: Document linux,usable-memory property Abhishek Tiwari
2025-03-13 16:10 ` Krzysztof Kozlowski [this message]
2025-03-13 18:57 ` Rob Herring
2025-07-15 10:12 ` Abhishek Tiwari
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=9c52990b-c8fd-440f-bd2c-bfa0e63c00fc@kernel.org \
--to=krzk@kernel.org \
--cc=abhitiwari@linux.microsoft.com \
--cc=abhitiwari@microsoft.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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