linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Barry Song <song.bao.hua@hisilicon.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH] Documentation/admin-guide: mark memmap parameter is supported by a few architectures
Date: Sun, 22 Nov 2020 15:13:03 +0200	[thread overview]
Message-ID: <20201122131303.GF8537@kernel.org> (raw)
In-Reply-To: <20201118014145.29596-1-song.bao.hua@hisilicon.com>

On Wed, Nov 18, 2020 at 02:41:45PM +1300, Barry Song wrote:
> early_param memmap is only implemented on X86, MIPS and XTENSA. To avoid
> wasting users’ time on trying this on platform like ARM, mark it clearly.
> 
> Signed-off-by: Barry Song <song.bao.hua@hisilicon.com>

Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>

> ---
>  * the background was that I spent one hour on using memmap on arm64, only
>    to find memmap= is not implemented on most architectures;
> 
>  Documentation/admin-guide/kernel-parameters.rst | 1 +
>  Documentation/admin-guide/kernel-parameters.txt | 2 +-
>  2 files changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/admin-guide/kernel-parameters.rst b/Documentation/admin-guide/kernel-parameters.rst
> index 6d421694d98e..06fb1b4aa849 100644
> --- a/Documentation/admin-guide/kernel-parameters.rst
> +++ b/Documentation/admin-guide/kernel-parameters.rst
> @@ -172,6 +172,7 @@ parameter is applicable::
>  	X86	Either 32-bit or 64-bit x86 (same as X86-32+X86-64)
>  	X86_UV	SGI UV support is enabled.
>  	XEN	Xen support is enabled
> +	XTENSA	xtensa architecture is enabled.
>  
>  In addition, the following text indicates that the option::
>  
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 526d65d8573a..8bdbc555f221 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -2709,7 +2709,7 @@
>  			option description.
>  
>  	memmap=nn[KMG]@ss[KMG]
> -			[KNL] Force usage of a specific region of memory.
> +			[KNL, X86, MIPS, XTENSA] Force usage of a specific region of memory.
>  			Region of memory to be used is from ss to ss+nn.
>  			If @ss[KMG] is omitted, it is equivalent to mem=nn[KMG],
>  			which limits max address to nn[KMG].
> -- 
> 2.25.1
> 

-- 
Sincerely yours,
Mike.

      reply	other threads:[~2020-11-22 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18  1:41 [PATCH] Documentation/admin-guide: mark memmap parameter is supported by a few architectures Barry Song
2020-11-22 13:13 ` Mike Rapoport [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=20201122131303.GF8537@kernel.org \
    --to=rppt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=song.bao.hua@hisilicon.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).