From: Joe Damato <jdamato@fastly.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 1/1] ioctl_epoll.2: New page describing epoll ioctl(2)
Date: Tue, 11 Jun 2024 10:58:26 -0700 [thread overview]
Message-ID: <ZmiQQm9sNfFboKsJ@LQ3V64L9R2> (raw)
In-Reply-To: <hjkeoyc4wa5amugp4sdbm2b4y4zxbgv4lie2ezyctagygnaetj@mjghmuldnpna>
On Tue, Jun 11, 2024 at 07:43:52PM +0200, Alejandro Colomar wrote:
> Hi Joe,
>
> On Tue, Jun 11, 2024 at 10:28:48AM GMT, Joe Damato wrote:
> > OK, I've included it twice -- once before the ioctls and once before
> > the struct, with a comment:
> >
> > .BR "#include <sys/epoll.h>" " /* Definition of " struct " "epoll_params " */"
>
> No comment here, please.
OK removed and switched to .B (instead of .BR).
> > .P
> > .B struct epoll_params {
> >
> > Hope that is OK! If not, let me know ;)
> >
> > > > > > Changed this to:
> > > > > >
> > > > > > retrieve on each poll attempt. This value cannot exceed
> > > > > > .B NAPI_POLL_WEIGHT
> > > > > > (which is 64 as of Linux 6.9), unless the process is run with
> > > > > > .B CAP_NET_ADMIN.
> > > > > >
> > > > > > How is that?
> > > > >
> > > > > Much better. (But still needs to use semantic newlines.)
> > > >
> > > > Hmm, I need to go back and re-read the semantic newline email because I made
> > > > this section look like this:
> > >
> > > You may want to also read this commit:
> > >
> > > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/man7/man-pages.7?id=6ff6f43d68164f99a8c3fb66f4525d145571310c>
> > >
> > > It includes a quote from Brian W. Kernighan, which is a little bit more
> > > detailed than man-pages(7) about it.
> >
> > I just read that and will continue read it a few more times. I will
> > try to better understand how to format the man page text as you've
> > explained.
> >
> > Please accept my apologies if I've still gotten it wrong in the v3,
> > I'm not quite sure I've totally wrapped my head around when/where
> > are good places to wrap long lines that exceed 80 characters.
>
> No problems; if there are only a few small issues, I'll fix them while
> applying. Otherwise, as long as you're patient, I am too. :)
>
> Clause boundaries aren't as easy to spot as sentence boundaries.
> Prepositions are usually good places. 'that' is usually a good place
> too. Separating the subject or an adverbial group from the rest of the
> sentence is also a good choice. But it's in the end a matter of taste.
> It's maybe easier to see the places where you wouldn't want to break it,
> such as:
>
> the maximum number of packets that the network
> stack will retrieve on each poll attempt.
>
> because 'network stack' is an noun group (or whatever it's called in
> English).
OK thanks for the examples.
I'll take another read through what I have and send a v3 shortly.
[...]
prev parent reply other threads:[~2024-06-11 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 23:12 [PATCH v2 0/1] ioctl_epoll.2: Add epoll ioctl documentation Joe Damato
2024-06-10 23:12 ` [PATCH v2 1/1] ioctl_epoll.2: New page describing epoll ioctl(2) Joe Damato
2024-06-10 23:45 ` Alejandro Colomar
2024-06-11 0:29 ` Joe Damato
2024-06-11 8:54 ` Alejandro Colomar
2024-06-11 12:24 ` G. Branden Robinson
2024-06-11 14:22 ` Alejandro Colomar
2024-06-11 15:42 ` G. Branden Robinson
2024-06-11 16:34 ` Joe Damato
2024-06-11 17:14 ` Alejandro Colomar
2024-06-11 17:28 ` Joe Damato
2024-06-11 17:43 ` Alejandro Colomar
2024-06-11 17:58 ` 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=ZmiQQm9sNfFboKsJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox