From: Joe Damato <jdamato@fastly.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 1/1] ioctl_eventpoll.2: New page describing epoll ioctl(2)
Date: Tue, 11 Jun 2024 13:47:57 -0700 [thread overview]
Message-ID: <Zmi3_Svw4j9u4dhL@LQ3V64L9R2> (raw)
In-Reply-To: <7fimwlnnzrkmrercgiiwmc5brbzrlgafbzlxij5dhg3rpctva5@hjh5ablva365>
On Tue, Jun 11, 2024 at 10:37:20PM +0200, Alejandro Colomar wrote:
> Hi Joe,
>
> On Tue, Jun 11, 2024 at 01:29:50PM GMT, Joe Damato wrote:
> > > > diff --git a/man/man2/ioctl_eventpoll.2 b/man/man2/ioctl_eventpoll.2
> > > > new file mode 100644
> > > > index 000000000..0fe03d6d4
> > > > --- /dev/null
> > > > +++ b/man/man2/ioctl_eventpoll.2
> > > > @@ -0,0 +1,173 @@
> > > > +.\" Copyright (c) 2024, Joe Damato
> > >
> > > 1d
> >
> > My apologies, but I am not sure what you mean by this. What does 1d
> > mean?
>
> I meant `sed -i 1d`. This line was redundant with line 2.
Ah, of course. I've removed that line above and left the line below
instead.
> > > > +.\" Copyright 2024, Joe Damato <jdamato@fastly.com>
> > > > +.\"
> > > > +.\" SPDX-License-Identifier: Linux-man-pages-copyleft
> > > > +.\"
>
> [...]
>
> > > Also, I'd like to align the member names according to
> > > <https://nginx.org/en/docs/dev/development_guide.html#code_style_variables>.
> > > That is, 2 spaces of minimum alignment, plus the necessary to make them
> > > all aligned (so 3 on the last).
> > >
> > > I'd like also 2 spaces minimum before the comments, instead of just 1.
> >
> > OK, based on the link you sent, I've aligned the start of each of
> > the types and then aligned the start of the field names. Lastly,
> > I've aligned the start of the comments for the first 3 fields, but
> > left the comment for the __pad just two spaces after the field name.
> >
> > Did you want the comment for __pad to be aligned to the comments for
> > the in-use fields above?
> >
> > This is what I have now, but I can insert space to move the pad comment over if
> > you like.
> >
> > .EX
> > .B struct epoll_params {
> > .BR " uint32_t busy_poll_usecs;" " /* Number of usecs to busy poll */"
> > .BR " uint16_t busy_poll_budget;" " /* Max packets per poll */"
> > .BR " uint8_t prefer_busy_poll;" " /* Boolean preference */"
> > \&
> > .BR " " "/* pad the struct to a multiple of 64bits */"
> > .BR " uint8_t __pad;" " /* Must be zero */"
> > .B };
> > .EE
>
> LGTM.
>
> [...]
>
> > > Please also add a STANDARDS section, which just says "Linux."
> >
> > OK added STANDARDS (in the order above) which just says Linux:
> >
> > .SH STANDARDS
> > .P
>
> .P after .SH is redundant.
Fixed.
Will push a v4 shortly after re-reading this one.
> > Linux.
> > .SH HISTORY
> >
> > > Regarding semantic newlines, it looks great. Thanks!
> >
> > Great!
>
> Have a lovely night!
> Alex
>
> --
> <https://www.alejandro-colomar.es/>
prev parent reply other threads:[~2024-06-11 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 19:12 [PATCH v3 0/1] ioctl_eventpoll.2: Add eventpoll ioctl documentation Joe Damato
2024-06-11 19:12 ` [PATCH v3 1/1] ioctl_eventpoll.2: New page describing epoll ioctl(2) Joe Damato
2024-06-11 20:07 ` Alejandro Colomar
2024-06-11 20:29 ` Joe Damato
2024-06-11 20:37 ` Alejandro Colomar
2024-06-11 20:47 ` Joe Damato [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=Zmi3_Svw4j9u4dhL@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.