public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>, linux-man@vger.kernel.org
Subject: Re: [PATCH] timespec.3type: tfix: use correct name for nanosecond field
Date: Wed, 4 Jan 2023 00:49:01 +0100	[thread overview]
Message-ID: <8d308ead-9efa-a040-adba-329297cb3bdc@gmail.com> (raw)
In-Reply-To: <20230103234534.48591-1-linux@weissschuh.net>


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

Hi Thomas,

On 1/4/23 00:45, Thomas Weißschuh wrote:
> The field is correctly called "tv_nsec" as it is also used in other
> places in the manpage.
> 
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>

Thanks.  Patch applied.  I had seen it, and I thought I had fixed it recently. 
It seems I didn't.

Cheers,

Alex

> ---
>   man3type/timespec.3type | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man3type/timespec.3type b/man3type/timespec.3type
> index fdddcc778d6c..7cd80ce8669b 100644
> --- a/man3type/timespec.3type
> +++ b/man3type/timespec.3type
> @@ -16,7 +16,7 @@ Standard C library
>   .PP
>   .B struct timespec {
>   .BR "    time_t  tv_sec;" "   /* Seconds */"
> -.BR "    long    tv_usec;" "  /* Nanoseconds [" 0 ", " 999999999 "] */"
> +.BR "    long    tv_nsec;" "  /* Nanoseconds [" 0 ", " 999999999 "] */"
>   .B };
>   .EE
>   .SH DESCRIPTION
> 
> base-commit: 7474e450de3dc6c2b96fadd3271b1643b4f094a6

-- 
<http://www.alejandro-colomar.es/>

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

      reply	other threads:[~2023-01-03 23:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 23:45 [PATCH] timespec.3type: tfix: use correct name for nanosecond field Thomas Weißschuh
2023-01-03 23:49 ` 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=8d308ead-9efa-a040-adba-329297cb3bdc@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux@weissschuh.net \
    /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