public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: y@shlinux1.ap.freescale.net
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
	tglx@linutronix.de, john.stultz@linaro.org,
	liu.y.victor@gmail.com, Liu Ying <Ying.Liu@freescale.com>
Subject: Re: [PATCH 1/1] ktime: Use macro NSEC_PER_USEC instead of a magic number
Date: Tue, 07 May 2013 10:15:05 +0200	[thread overview]
Message-ID: <5188B809.5060803@redhat.com> (raw)
In-Reply-To: <1367844135-31383-1-git-send-email-y>

On 05/06/2013 02:42 PM, y@shlinux1.ap.freescale.net wrote:
> From: Liu Ying <Ying.Liu@freescale.com>

Nitpick:

If you only have 1 patch, then you don't need "1/1" in the subject.
The term magic number here might be a little exaggerated, not so
magic actually. :-)

But, in general I agree that we could do that also since it is used
elsewhere in the same header file. Thus, this might be more consistent.

> We've got the macro NSEC_PER_USEC defined in header file
> include/linux/time.h. To make the code decent, this patch
> replaces the magic number 1000 to convert bewteen a time
> value in microseconds and one in nanoseconds with the
> macro NSEC_PER_USEC.
>
> Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Daniel Borkmann <dborkman@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: John Stultz <john.stultz@linaro.org>
> ---
>   include/linux/ktime.h |    7 ++++---
>   1 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/ktime.h b/include/linux/ktime.h
> index bbca128..5de963d 100644
> --- a/include/linux/ktime.h
> +++ b/include/linux/ktime.h
> @@ -229,7 +229,8 @@ static inline ktime_t timespec_to_ktime(const struct timespec ts)
>   static inline ktime_t timeval_to_ktime(const struct timeval tv)
>   {
>   	return (ktime_t) { .tv = { .sec = (s32)tv.tv_sec,
> -				   .nsec = (s32)tv.tv_usec * 1000 } };
> +				   .nsec = (s32)tv.tv_usec *
> +					   (s32)NSEC_PER_USEC} };

Nitpick: Likely, this could be reduced to one cast only.

Otherwise looks good.

>   }
>
>   /**
> @@ -320,12 +321,12 @@ static inline s64 ktime_us_delta(const ktime_t later, const ktime_t earlier)
>
>   static inline ktime_t ktime_add_us(const ktime_t kt, const u64 usec)
>   {
> -	return ktime_add_ns(kt, usec * 1000);
> +	return ktime_add_ns(kt, usec * NSEC_PER_USEC);
>   }
>
>   static inline ktime_t ktime_sub_us(const ktime_t kt, const u64 usec)
>   {
> -	return ktime_sub_ns(kt, usec * 1000);
> +	return ktime_sub_ns(kt, usec * NSEC_PER_USEC);
>   }
>
>   extern ktime_t ktime_add_safe(const ktime_t lhs, const ktime_t rhs);
>

  reply	other threads:[~2013-05-07  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 12:42 [PATCH 1/1] ktime: Use macro NSEC_PER_USEC instead of a magic number y
2013-05-07  8:15 ` Daniel Borkmann [this message]
     [not found]   ` <CA+8Hj83_6Feq8KVSJh+E=R35wm2ZkF+uGWxcJV7XZsOxdze41A@mail.gmail.com>
     [not found]     ` <CA+8Hj838CfaAKjdLtO2zdZ5DJP10a0QCzhYJbZ3GqQhmE5MZzw@mail.gmail.com>
2013-05-07  9:12       ` Daniel Borkmann

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=5188B809.5060803@redhat.com \
    --to=dborkman@redhat.com \
    --cc=Ying.Liu@freescale.com \
    --cc=davem@davemloft.net \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liu.y.victor@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=y@shlinux1.ap.freescale.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