[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANDhNCoNXO7phZj4zjpMWCA2OsK3EgTUenUuX0z-KAejgqu1Dg@mail.gmail.com>
Date: Thu, 11 May 2023 20:12:52 -0700
From: John Stultz <jstultz@...gle.com>
To: walter.chang@...iatek.com
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
"Maciej W . Rozycki" <macro@...am.me.uk>,
wsd_upstream@...iatek.com, stanley.chu@...iatek.com,
Chun-hung.Wu@...iatek.com, Freddy.Hsin@...iatek.com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH linux-next v3 1/4] time/sched_clock: Export sched_clock_register()
On Wed, Apr 19, 2023 at 12:49 AM <walter.chang@...iatek.com> wrote:
>
> From: Chun-Hung Wu <chun-hung.wu@...iatek.com>
>
> clocksource driver may use sched_clock_register()
> to resigter itself as a sched_clock source.
> Export it to support building such driver
> as module, like timer-mediatek.c
>
> Signed-off-by: Chun-Hung Wu <chun-hung.wu@...iatek.com>
Sorry for the late reply, I was traveling when I got your mail.
Thanks for your iterations on this series.
I'm ok with these, assuming the folks who maintain the timer-mediatek
driver don't have any more objections.
So for the first three patches:
Acked-by: John Stultz <jstultz@...gle.com>
thanks
-john
Powered by blists - more mailing lists