[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2203091809100.47558@angie.orcam.me.uk>
Date: Wed, 9 Mar 2022 18:13:14 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Mike Rapoport <rppt@...nel.org>
cc: Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Randy Dunlap <rdunlap@...radead.org>,
Sergey Shtylyov <s.shtylyov@....ru>,
Tiezhu Yang <yangtiezhu@...ngson.cn>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
linux-doc@...r.kernel.org, linux-mips@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] docs/kernel-parameters: update description of mem=
On Wed, 9 Mar 2022, Mike Rapoport wrote:
> From: Mike Rapoport <rppt@...ux.ibm.com>
>
> The existing description of mem= does not cover all the cases and
> differences between how architectures treat it.
>
> Extend the description to match the code.
This:
> + mem=nn[KMG] [HEXAGON] Set the memory size.
> + Must be specified, otherwise memory size will be 0.
> +
I guess would better be folded into the other `mem=nn[KMG]' description
above, possibly between [ARM64] and [X86] so as to keep the order roughly
alphabetic.
Maciej
Powered by blists - more mailing lists