From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Mike Rapoport <rppt@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Randy Dunlap <rdunlap@infradead.org>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-doc@vger.kernel.org, linux-mips@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs/kernel-parameters: update description of mem=
Date: Wed, 9 Mar 2022 18:54:39 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.21.2203091851460.47558@angie.orcam.me.uk> (raw)
In-Reply-To: <Yijyf0pac9h14rok@kernel.org>
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
prev parent reply other threads:[~2022-03-09 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 17:22 Mike Rapoport
2022-03-09 18:13 ` Maciej W. Rozycki
2022-03-09 18:31 ` Mike Rapoport
2022-03-09 18:54 ` Maciej W. Rozycki [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=alpine.DEB.2.21.2203091851460.47558@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=s.shtylyov@omp.ru \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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