All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 2/2] fmod.3: add example section
Date: Wed, 13 Sep 2023 18:00:20 +0200	[thread overview]
Message-ID: <856ffe52-5fb0-4228-a7d6-e52505ffe47e@kernel.org> (raw)
In-Reply-To: <20230904185405.89180-2-jengelh@inai.de>


[-- Attachment #1.1: Type: text/plain, Size: 759 bytes --]

Hi Jan,

On 2023-09-04 20:53, Jan Engelhardt wrote:
> Signed-off-by: Jan Engelhardt <jengelh@inai.de>

Patch set applied.

Thanks,
Alex

> ---
>  man3/fmod.3 | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/man3/fmod.3 b/man3/fmod.3
> index 944bf4167..13236c425 100644
> --- a/man3/fmod.3
> +++ b/man3/fmod.3
> @@ -165,5 +165,11 @@ to
>  .B EDOM
>  when a domain error occurred for an infinite
>  .IR x .
> +.SH EXAMPLES
> +The call "fmod(372, 360)" returns 348.
> +.PP
> +The call "fmod(-372, 360)" returns -12.
> +.PP
> +The call "fmod(-372, -360)" also returns -12.
>  .SH SEE ALSO
>  .BR remainder (3)

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-09-13 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 13:49 [PATCH 1/2] fmod.3: add note how to obtain modulus/LPR Jan Engelhardt
2023-07-24 13:49 ` [PATCH 2/2] fmod.3: add example section Jan Engelhardt
2023-07-28 20:26 ` [PATCH 1/2] fmod.3: add note how to obtain modulus/LPR Alejandro Colomar
2023-09-04 18:53   ` [PATCH v2 " Jan Engelhardt
2023-09-04 18:53     ` [PATCH v2 2/2] fmod.3: add example section Jan Engelhardt
2023-09-13 16:00       ` Alejandro Colomar [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=856ffe52-5fb0-4228-a7d6-e52505ffe47e@kernel.org \
    --to=alx@kernel.org \
    --cc=jengelh@inai.de \
    --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.