From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Alexander Dahl <ada@thorsis.com>,
linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.2.9-rt3
Date: Wed, 21 Aug 2019 16:58:37 +0200 [thread overview]
Message-ID: <20190821145837.GD27031@piout.net> (raw)
In-Reply-To: <20190821144230.knlyrnxz62d75hcb@linutronix.de>
On 21/08/2019 16:42:30+0200, Sebastian Andrzej Siewior wrote:
> On 2019-08-21 16:21:10 [+0200], Alexandre Belloni wrote:
> > I'm not sure it is worth it as the issue is introduced by
> > clocksource-tclib-allow-higher-clockrates.patch. Shouldn't we fix it
> > directly?
>
> you want to get rid of CONFIG_ATMEL_TCB_CLKSRC_USE_SLOW_CLOCK and use
> the highest possible frequency by default?
>
No, I meant the issue fixed by clocksource-tclib-add-proper-depend.patch
is introduced by clocksource-tclib-allow-higher-clockrates.patch so I
would think fixing clocksource-tclib-allow-higher-clockrates.patch is
preferable than having a separate patch.
But maybe you meant you wanted a patch to fix
clocksource-tclib-allow-higher-clockrates.patch
Hopefully, one day we will have a solution for that upstream (i.e. being
able to configure the clocksource and clockevent resolutions).
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-21 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 15:36 [ANNOUNCE] v5.2.9-rt3 Sebastian Andrzej Siewior
2019-08-19 11:03 ` Alexander Dahl
2019-08-20 15:44 ` Alexandre Belloni
2019-08-21 13:25 ` Sebastian Andrzej Siewior
2019-08-21 14:21 ` Alexandre Belloni
2019-08-21 14:42 ` Sebastian Andrzej Siewior
2019-08-21 14:58 ` Alexandre Belloni [this message]
2019-08-21 15:15 ` Sebastian Andrzej Siewior
2019-08-21 16:19 ` Alexandre Belloni
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=20190821145837.GD27031@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=ada@thorsis.com \
--cc=bigeasy@linutronix.de \
--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.