linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avinesh Kumar <akumar@suse.de>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] mmap.2: fix missing text
Date: Mon, 28 Aug 2023 18:58:47 +0530	[thread overview]
Message-ID: <7094633.DmTEyPuAzL@localhost> (raw)
In-Reply-To: <284f129a-5d21-76fa-7cf5-851512ee5914@kernel.org>

Hi Alex,

On Friday, August 25, 2023 11:22:29 PM IST Alejandro Colomar wrote:
> Hi Avinesh,
> 
> On 2023-08-25 17:59, Avinesh Kumar wrote:
> > Signed-off-by: Avinesh Kumar <akumar@suse.de>
> > ---
> > 
> >  man2/mmap.2 | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/man2/mmap.2 b/man2/mmap.2
> > index d0530be0f..9de6b2796 100644
> > --- a/man2/mmap.2
> > +++ b/man2/mmap.2
> > @@ -629,6 +629,7 @@ and is not a member of the
> > 
> >  group; see the description of
> >  .I /proc/sys/vm/sysctl_hugetlb_shm_group
> >  in
> > 
> > +.BR proc (5).
> 
> Was this text accidentally lost in some patch, or was it never added?
> If it was there once, please add a "Fixes: ..." tag for it.
I am not sure if it was ever there.
> 
> Also, proc(5) was recently cut into little sashimi pieces.  You want
> to refer to proc_sys(5).
Ah.. Thanks for pointing this out, I just checked that thread. I'll send the 
updated patch if you are fine with no "Fixes:" tag for this.
> 
> Cheers,
> Alex
> 
> >  .TP
> >  .B ETXTBSY
> >  .B MAP_DENYWRITE

--
Regards,
Avinesh




  reply	other threads:[~2023-08-28 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 15:59 [PATCH] mmap.2: fix missing text Avinesh Kumar
2023-08-25 17:52 ` Alejandro Colomar
2023-08-28 13:28   ` Avinesh Kumar [this message]
2023-08-29  9:43     ` Alejandro Colomar
2023-08-29  9:47       ` Alejandro Colomar
2023-08-29 10:32       ` Avinesh Kumar

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=7094633.DmTEyPuAzL@localhost \
    --to=akumar@suse.de \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).