[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2203091851460.47558@angie.orcam.me.uk>
Date: Wed, 9 Mar 2022 18:54:39 +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:
> > 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=
I don't know how other people, but I'd not expect duplicate entries in
this file and would simply miss any subsequent one(s). Even more so if
not adjacent such as in this case.
Maciej
Powered by blists - more mailing lists