From: Calvin Zhang <calvinzhang.cool@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Calvin Zhang <calvinzhang.cool@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: make MAX_RESERVED_REGIONS configurable
Date: Mon, 15 Nov 2021 15:14:21 +0800 [thread overview]
Message-ID: <YZIIzcO+MPbNH3qR@debian> (raw)
In-Reply-To: <18eb2d82-d3b3-79ec-9c20-c5c5cf5cab52@infradead.org>
On Sun, Nov 14, 2021 at 10:40:29PM -0800, Randy Dunlap wrote:
>On 11/14/21 10:35 PM, Calvin Zhang wrote:
>> diff --git a/drivers/of/Kconfig b/drivers/of/Kconfig
>> index 80b5fd44ab1c..591b2c4d9dd0 100644
>> --- a/drivers/of/Kconfig
>> +++ b/drivers/of/Kconfig
>> @@ -73,6 +73,16 @@ config OF_IRQ
>> config OF_RESERVED_MEM
>> def_bool OF_EARLY_FLATTREE
>> +config OF_MAX_RESERVED_REGIONS
>> + int "Maximum count of reserved regions"
>> + depends on OF_RESERVED_MEM
>> + default 64
>> + help
>> + Reserved regions in /reserved-memory node includes static
>> + reservations with fixed location and dynamic ones for device
>> + cma regions. This parameter sets the maximum number of reserved
>
> CMA
>
>(as is used in mm/Kconfig)
>
>> + regions in the system.
>
>Also, all 4 lines of the help text should be indented with
>one tab + 2 spaces, not all spaces.
>
Thanks for the review. I will send a v2.
>
>thanks.
>--
>~Randy
>
prev parent reply other threads:[~2021-11-15 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 6:35 [PATCH] of: make MAX_RESERVED_REGIONS configurable Calvin Zhang
2021-11-15 6:40 ` Randy Dunlap
2021-11-15 7:14 ` Calvin Zhang [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=YZIIzcO+MPbNH3qR@debian \
--to=calvinzhang.cool@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
/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).