[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yijyf0pac9h14rok@kernel.org>
Date:   Wed, 9 Mar 2022 20:31:27 +0200
From:   Mike Rapoport <rppt@...nel.org>
To:     "Maciej W. Rozycki" <macro@...am.me.uk>
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, Mar 09, 2022 at 06:13:14PM +0000, Maciej W. Rozycki wrote:
> 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.
I deliberately put hexagon separately because it stands out being the only
arch that has no other means of memory detection except mem=
 
>   Maciej
-- 
Sincerely yours,
Mike.
Powered by blists - more mailing lists
 
