From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] system_data_types.7: Add imaxdiv_t
Date: Thu, 24 Sep 2020 12:08:16 +0200 [thread overview]
Message-ID: <c74b40c6-03c6-86d3-74b7-0697528f357a@gmail.com> (raw)
In-Reply-To: <20200924095854.77221-1-colomar.6.4.3@gmail.com>
On 9/24/20 11:58 AM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
> man7/system_data_types.7 | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
Thanks, Alex. Patch applied.
Cheers,
Michael
> diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
> index ea3e25175..c00345741 100644
> --- a/man7/system_data_types.7
> +++ b/man7/system_data_types.7
> @@ -182,6 +182,28 @@ Conforming to: POSIX.1-2001 and later.
> See also:
> .BR getpriority (2),
> .BR waitid (2)
> +.\"------------------------------------- imaxdiv_t --------------------/
> +.TP
> +.I imaxdiv_t
> +.IP
> +Include:
> +.IR <inttypes.h> .
> +.IP
> +.EX
> +typedef struct {
> + intmax_t quot; /* Quotient */
> + intmax_t rem; /* Remainder */
> +} imaxdiv_t;
> +.EE
> +.IP
> +It is the type of the value returned by the
> +.I imaxdiv (3)
> +function.
> +.IP
> +Conforming to: C99 and later; POSIX.1-2001 and later.
> +.IP
> +See also:
> +.BR imaxdiv (3)
> .\"------------------------------------- pid_t ------------------------/
> .TP
> .I pid_t
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-09-24 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 9:58 [PATCH 1/2] system_data_types.7: Add imaxdiv_t Alejandro Colomar
2020-09-24 9:58 ` [PATCH 2/2] imaxdiv_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-24 10:08 ` Michael Kerrisk (man-pages)
2020-09-24 10:08 ` Michael Kerrisk (man-pages) [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=c74b40c6-03c6-86d3-74b7-0697528f357a@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--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