From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.10.9-rt5
Date: Fri, 23 Aug 2013 13:21:17 -0700 [thread overview]
Message-ID: <5217C43D.6090909@localhost> (raw)
In-Reply-To: <20130823175628.GA9130@linutronix.de>
On 08/23/2013 10:56 AM, Sebastian Andrzej Siewior wrote:
> * Fernando Lopez-Lezcano | 2013-08-23 10:18:08 [-0700]:
>
>> Please post a patch when/if you have it so I can retry the build...
>> Thanks for taking a look at this!
>
> Does this fix your trobule?
Yes, it does, thanks! Builds, installs and boots the x86_64 kernel (I
did not test the i686 build, I don't have a 32 machine to test).
-- Fernando
> diff --git a/drivers/misc/hwlat_detector.c b/drivers/misc/hwlat_detector.c
> index 0bfa40d..6f61d5f 100644
> --- a/drivers/misc/hwlat_detector.c
> +++ b/drivers/misc/hwlat_detector.c
> @@ -220,7 +220,7 @@ static struct sample *buffer_get_sample(struct sample *sample)
> #else
> #define time_type u64
> #define time_get() trace_clock_local()
> -#define time_to_us(x) ((x) / 1000)
> +#define time_to_us(x) div_u64(x, 1000)
> #define time_sub(a, b) ((a) - (b))
> #define init_time(a, b) a = b
> #define time_u64(a) a
prev parent reply other threads:[~2013-08-23 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 18:21 [ANNOUNCE] 3.10.9-rt5 Sebastian Andrzej Siewior
2013-08-22 18:24 ` Sebastian Andrzej Siewior
2013-08-31 21:00 ` Paul E. McKenney
2013-08-22 18:53 ` Steven Rostedt
2013-08-23 7:06 ` Sebastian Andrzej Siewior
2013-08-23 5:50 ` Fernando Lopez-Lezcano
2013-08-23 7:08 ` Sebastian Andrzej Siewior
2013-08-23 17:18 ` Fernando Lopez-Lezcano
2013-08-23 17:56 ` Sebastian Andrzej Siewior
2013-08-23 20:21 ` Fernando Lopez-Lezcano [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=5217C43D.6090909@localhost \
--to=nando@ccrma.stanford.edu \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.