From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Sami Pietikäinen" <Sami.Pietikainen@wapice.com>
Cc: Michael Langfinger <linux-rt-users@langfinger.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.12.0-rt2
Date: Fri, 29 Nov 2013 17:13:38 +0100 [thread overview]
Message-ID: <20131129161338.GF31099@linutronix.de> (raw)
In-Reply-To: <EBD2DE4ADA47B94E831AED12A4B0CADA67EF1DCA@edb1.wapice.localdomain>
* Sami Pietikäinen | 2013-11-25 13:21:13 [+0000]:
>In clocksource-tclib-allow-higher-clockrates.patch the clockevent device frequency is
>stored to a local variable but never written to the tc_clkevt_device struct (setup_clkevents function).
Thanks, no idea how I could overlook this.
>Fix: replace local freq variable with clkevt.freq in setup_clkevents function.
>I also renamed clk32k_divisor_idx to divisor_idx because the 32k frequency is not
>hard coded in RT.
Yeah, the right thing to do, Applied
>
>BR,
>Sami Pietikäinen
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-29 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 19:46 [ANNOUNCE] 3.12.0-rt2 Sebastian Andrzej Siewior
2013-11-16 21:26 ` Pavel Vasilyev
2013-11-19 7:38 ` Sami Pietikäinen
2013-11-22 14:23 ` Sebastian Andrzej Siewior
2013-11-24 10:15 ` Michael Langfinger
2013-11-25 8:23 ` Sami Pietikäinen
2013-11-25 13:21 ` Sami Pietikäinen
2013-11-29 16:13 ` Sebastian Andrzej Siewior [this message]
2013-11-21 20:44 ` [ANNOUNCE] 3.2.52-rt73 Pavel Vasilyev
2013-11-22 14:56 ` Sebastian Andrzej Siewior
2013-11-22 21:11 ` [ANNOUNCE] 3.12.1-rt4 Sebastian Andrzej Siewior
2013-12-01 22:25 ` Pavel Vasilyev
2013-12-02 8:43 ` Sebastian Andrzej Siewior
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=20131129161338.GF31099@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=Sami.Pietikainen@wapice.com \
--cc=linux-rt-users@langfinger.org \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).