public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Zijun Zhao <zijunzhao@google.com>
Cc: linux-man@vger.kernel.org, enh <enh@google.com>
Subject: Re: [PATCH] Fix the man page
Date: Sat, 8 Jul 2023 20:37:18 +0200	[thread overview]
Message-ID: <bf4dd8ed-ded3-6fe0-d3fa-afa63164bc4c@kernel.org> (raw)
In-Reply-To: <e7083e0d-92c2-ae07-7ff5-f7fa1ca91be6@kernel.org>


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

Hi Zijun,

Here goes some review of the patch.

> Subject: [PATCH] Modify the documentation of gettimeofday()

Please use 'gettimeofday.2:' as a prefix for the subject line,
and have a more descriptive subject (most patches do modify
the documentation, but how?).

See CONTRIBUTING:
        -  Write a suitable subject line.  Make sure to mention the
           name(s) of the page(s) being patched.  Example:

              [patch] shmop.2: Add "(void *)" cast to RETURN VALUE

> 
> We find tv arg is allowed to be null in bionic so make the documentation more clear.
> 
> Cc: enh <enh@google.com>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
> ---
>  man2/gettimeofday.2 | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/man2/gettimeofday.2 b/man2/gettimeofday.2
> index 9d134fa49..43f3fd9ff 100644
> --- a/man2/gettimeofday.2
> +++ b/man2/gettimeofday.2
> @@ -175,6 +175,7 @@ .SS C library/kernel differences
>  .BR gettimeofday ()
>  is provided in the
>  .BR vdso (7).

A blank line should introduce the new paragraph, so add '.PP'.

> +The kernel accepts null for both time and timezone. The timezone argument is ignored by glibc and musl, and not passed to/from the kernel. Android's bionic passes the timezone argument to/from the kernel, but Android does not update the kernel timezone based on the device timezone in Settings, so the kernel's timezone is typically UTC.

Please respect the 80-column right margin.  If you use vim(1),
this may be useful to you:

     set colorcolumn=73,81

Also, please use semantic newlines.  See man-pages(7):

    Use semantic newlines
        In  the  source of a manual page, new sentences should be
        started on new lines, long sentences should be split into
        lines at clause breaks (commas, semicolons,  colons,  and
        so on), and long clauses should be split at phrase bound‐
        aries.   This  convention,  sometimes  known as "semantic
        newlines", makes it easier to see the effect of  patches,
        which often operate at the level of individual sentences,
        clauses, or phrases.

Cheers,
Alex

>  .SH STANDARDS
>  .TP
>  .BR gettimeofday ()
> -- 
> 2.40.1
> 

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

  reply	other threads:[~2023-07-08 18:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 23:20 [PATCH] Fix the man page Zijun Zhao
2023-05-18 23:27 ` Zijun Zhao
2023-05-18 23:30   ` enh
2023-05-19  8:03     ` Alejandro Colomar
2023-05-19 22:21       ` enh
2023-05-19 22:41         ` Alejandro Colomar
2023-06-05 19:03           ` Zijun Zhao
2023-06-16 21:10             ` Zijun Zhao
     [not found]               ` <CAJgzZoqS-QJWX87P5B1LQxCktm9BAVfVVBwBxV87RhmQg0fsdg@mail.gmail.com>
2023-06-16 22:26                 ` enh
2023-07-08 18:02                   ` Alejandro Colomar
2023-07-08 18:37                     ` Alejandro Colomar [this message]
2023-07-11 23:48                       ` Zijun Zhao
2023-07-15 16:13                         ` Alejandro Colomar
2023-07-27 18:33                           ` Zijun Zhao
2023-07-28 20:48                             ` Alejandro Colomar
2023-07-28 20:58                               ` Zijun Zhao
2023-06-20 18:21           ` Zijun Zhao
2023-07-28 20:41             ` 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=bf4dd8ed-ded3-6fe0-d3fa-afa63164bc4c@kernel.org \
    --to=alx@kernel.org \
    --cc=enh@google.com \
    --cc=linux-man@vger.kernel.org \
    --cc=zijunzhao@google.com \
    /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