linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Wupeng Ma <mawupeng1@huawei.com>,
	akpm@linux-foundation.org, corbet@lwn.net
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc: update params of memhp_default_state=
Date: Wed, 2 Aug 2023 09:59:24 +0200	[thread overview]
Message-ID: <89efb68c-b6e7-f652-8dc7-310c5f48a0a9@redhat.com> (raw)
In-Reply-To: <20230802074312.2111074-1-mawupeng1@huawei.com>

On 02.08.23 09:43, Wupeng Ma wrote:
> From: Ma Wupeng <mawupeng1@huawei.com>
> 
> Commit 5f47adf762b7 ("mm/memory_hotplug: allow to specify a default
> online_type") allows to specify a default online_type which make
> online memory to kernel or movable zone possible but fail to update
> to doc. Update doc to fit this change.
> 
> Signed-off-by: Ma Wupeng <mawupeng1@huawei.com>
> ---
>   Documentation/admin-guide/kernel-parameters.txt | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index a1457995fd41..09bad9c62f41 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -3105,7 +3105,7 @@
>   			[KNL,SH] Allow user to override the default size for
>   			per-device physically contiguous DMA buffers.
>   
> -	memhp_default_state=online/offline
> +	memhp_default_state=online/offline/online_kernel/online_movable
>   			[KNL] Set the initial state for the memory hotplug
>   			onlining policy. If not specified, the default value is
>   			set according to the

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Cheers,

David / dhildenb


  reply	other threads:[~2023-08-02  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02  7:43 [PATCH] doc: update params of memhp_default_state= Wupeng Ma
2023-08-02  7:59 ` David Hildenbrand [this message]
2023-08-11 20:31 ` Jonathan Corbet

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=89efb68c-b6e7-f652-8dc7-310c5f48a0a9@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mawupeng1@huawei.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).