linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alex Henrie <alexhenrie24@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, bgeffon@google.com,
	linux-mm@kvack.org,  branden@debian.org
Subject: Re: [PATCH] mremap.2: Update information about MREMAP_DONTUNMAP restrictions
Date: Sun, 10 Nov 2024 23:07:48 -0700	[thread overview]
Message-ID: <CAMMLpeTC-27K0i_Nd-7Rk+25QZzcEJPxGHay5M7Skm-kp2QsWQ@mail.gmail.com> (raw)
In-Reply-To: <fqpd2bawfx7grb7mt5jcskvkht7ntnm3mmgvskwziav4remdmj@rkshuokqjupa>

On Tue, Nov 5, 2024 at 4:50 AM Alejandro Colomar <alx@kernel.org> wrote:
>
> Hi Alex,

Bon dia Alejandro, és un plaer parlar amb tu de nou!

> On Mon, Nov 04, 2024 at 09:16:41PM GMT, Alex Henrie wrote:

> > diff --git a/man/man2/mremap.2 b/man/man2/mremap.2
> > index 53e0bcf2d..b99ab9492 100644
> > --- a/man/man2/mremap.2
> > +++ b/man/man2/mremap.2
> > @@ -106,7 +106,13 @@ remaps a mapping to a new address but does not unmap the mapping at
> >  .IP
> >  The
> >  .B MREMAP_DONTUNMAP
> > -flag can be used only with private anonymous mappings
> > +flag can only be used with mappings that are not
>
> I find the position of "only" a bit inconsistent here.  It probably
> would be more appropriate right before "with".  (I'm wondering if I put
> "probably" in the right place too... :)

It probably is slightly more clear to say "can be used only with..."
instead of "can only be used with...". I'll make that change in v2.

> > +.BR VM_DONTEXPAND
>
> Please use .B, not .BR.  You'll find that BR causes a warning in that
> file, if you run `make build-all`:
>
>         $ make build-all -j24 -k
>         TROFF           .tmp/man/man2/mremap.2.cat.set
>         an.tmac:.tmp/man/man2/mremap.2:42: style: .BR expects at least 2 arguments, got 1
>         make: *** [/home/alx/src/linux/man-pages/man-pages/contrib/share/mk/build/catman/troff.mk:65: .tmp/man/man2/mremap.2.cat.set] Error 1
>         make: *** Deleting file '.tmp/man/man2/mremap.2.cat.set'
>         make: Target 'build-all' not remade because of errors.
>
> (You'll need to run a sufficiently recent system that includes
>  groff-1.23.0, such as Debian Sid.)

Will do, thanks for the tip.

-Alex


  reply	other threads:[~2024-11-11  6:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  4:16 Alex Henrie
2024-11-05 11:50 ` Alejandro Colomar
2024-11-11  6:07   ` Alex Henrie [this message]
2024-11-11  6:10 ` [PATCH man-pages v2] " Alex Henrie
2024-11-12 23:35   ` Alejandro Colomar

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=CAMMLpeTC-27K0i_Nd-7Rk+25QZzcEJPxGHay5M7Skm-kp2QsWQ@mail.gmail.com \
    --to=alexhenrie24@gmail.com \
    --cc=alx@kernel.org \
    --cc=bgeffon@google.com \
    --cc=branden@debian.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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