mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: arnd@arndb.de, john.stultz@linaro.org,
	linux-kernel@vger.kernel.org, y2038@lists.linaro.org
Subject: Re: [PATCH v4 01/25] linux/time64.h:Introduce the 'struct itimerspec64' for 64bit
Date: Tue, 2 Jun 2015 21:19:35 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1506021720140.20347@nanos> (raw)
In-Reply-To: <1433159306-4589-1-git-send-email-baolin.wang@linaro.org>

On Mon, 1 Jun 2015, Baolin Wang wrote:

> Subject: linux/time64.h:Introduce the 'struct itimerspec64' for 64bit

This subject line is wrong in several aspects:

 - linux/time64.h is a file name and does not describe the subsystem
   you are changing. 'time:' is the proper choice here

 - Missing space between colon and first word of the sentence

 - What means struct itimerspec64 for 64bit? Is this a 64bit only
   variant or what?


"Subject: time: Introduce struct itimerspec64"

is the proper subject line as it names the subsystem (time) and tells
clearly what the patch does.

> This patch introduces the 'struct itimerspec64' for 64bit to replace itimerspec,

Again: 'for 64bit' is really wrong here.

> and also introduces the conversion methods: itimerspec64_to_itimerspec() and
> itimerspec_to_itimerspec64(), that makes itimerspec ready for 2038 year.

You explain in great length WHAT the patch is doing, which is
pointless because one can see that from the patch itself. You should
explain WHY you are doing this first.

"itimerspec is not year 2038 safe on 32bit systems due to the
 limitation of the struct timespec members. Introduce itimerspec64
 which uses struct timespec64 instead and provide conversion
 functions"

Hmm?


> +struct itimerspec64 {
> +	struct timespec64 it_interval;  /* timer period */
> +	struct timespec64 it_value;     /* timer expiration */

I really hate tail comments. If you want to document your structure
use proper KernelDoc for it.

Thanks,

	tglx

      reply	other threads:[~2015-06-02 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 11:48 Baolin Wang
2015-06-02 19:19 ` Thomas Gleixner [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=alpine.DEB.2.11.1506021720140.20347@nanos \
    --to=tglx@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=baolin.wang@linaro.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=y2038@lists.linaro.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

all inboxes | Powered by JetHome®