From: Brian Norris <briannorris@chromium.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-man@vger.kernel.org
Subject: Re: [PATCH v2 2/2] sched_setattr.2: Document sched_util_{min,max}
Date: Thu, 13 Jun 2024 13:29:44 -0700 [thread overview]
Message-ID: <ZmtWuBD51thBxnBK@google.com> (raw)
In-Reply-To: <v4beebxguvvbhjgroqb7erykafxuez3svqf5pavvi6bmfjvuup@xsaim44xgdx6>
On Thu, Jun 13, 2024 at 12:15:55AM +0200, Alejandro Colomar wrote:
> On Wed, Jun 12, 2024 at 01:44:53PM GMT, Brian Norris wrote:
> > +maximum frequency and is represented by a utilization value of
> > +0.2 * 1024 = 205.
>
> This should go in italics.
>
> $ MANWIDTH=72 man man-pages | sed -n '/Expressions/,/^$/p'
> Expressions, if not written on a separate indented line, should be
> specified in italics. Again, the use of nonbreaking spaces may be
> appropriate if the expression is inlined with normal text.
Regarding the nonbreaking spaces part: I'm not too practiced with groff,
but the wording around the \[ti] character is confusing. AFAICT, I
actually need to spell my expression like the following?
0.2\~*\~1024\~=\~205
At least, with trial and error, that's what appears to render correctly,
whereas \[ti] renders as a literal tilde. Is man-pages.7 [1] incorrect?
Brian
[1] from `man man-pages`:
"In this case, it may be worth using nonbreaking spaces (\[ti]) at
suitable places in the command."
next prev parent reply other threads:[~2024-06-13 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 20:44 [PATCH v2 1/2] sched_setattr: Break EINVAL into separate blocks Brian Norris
2024-06-12 20:44 ` [PATCH v2 2/2] sched_setattr.2: Document sched_util_{min,max} Brian Norris
2024-06-12 22:15 ` Alejandro Colomar
2024-06-13 20:29 ` Brian Norris [this message]
2024-06-13 20:41 ` G. Branden Robinson
2024-06-13 21:31 ` Alejandro Colomar
2024-06-13 0:02 ` [PATCH v2 1/2] sched_setattr: Break EINVAL into separate blocks 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=ZmtWuBD51thBxnBK@google.com \
--to=briannorris@chromium.org \
--cc=alx@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-man@vger.kernel.org \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.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