From: Ingo Molnar <mingo@elte.hu>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Paul Menage <menage@google.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] CFS : Use NSEC_PER_MSEC and NSEC_PER_SEC in kernel/sched.c and kernel/sysctl.c
Date: Wed, 31 Oct 2007 11:20:35 +0100 [thread overview]
Message-ID: <20071031102035.GD5817@elte.hu> (raw)
In-Reply-To: <47280DE6.7030606@cosmosbay.com>
* Eric Dumazet <dada1@cosmosbay.com> wrote:
> 1) hardcoded 1000000000 value is used five times in places where
> NSEC_PER_SEC might be more readable.
>
> 2) A conversion from nsec to msec uses the hardcoded 1000000 value, which
> is a candidate for NSEC_PER_MSEC.
>
> Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
thanks, applied.
Ingo
prev parent reply other threads:[~2007-10-31 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 5:08 [PATCH] CFS : Use NSEC_PER_MSEC and NSEC_PER_SEC in kernel/sched.c and kernel/sysctl.c Eric Dumazet
2007-10-31 10:20 ` Ingo Molnar [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=20071031102035.GD5817@elte.hu \
--to=mingo@elte.hu \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@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