From: Alexandre Mergnat <amergnat@baylibre.com>
To: walter.chang@mediatek.com,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"Maciej W . Rozycki" <macro@orcam.me.uk>,
John Stultz <jstultz@google.com>
Cc: wsd_upstream@mediatek.com, stanley.chu@mediatek.com,
Chun-hung.Wu@mediatek.com, Freddy.Hsin@mediatek.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v5 4/4] clocksource/drivers/timer-mediatek: Make timer-mediatek become loadable module
Date: Tue, 23 May 2023 13:28:23 +0200 [thread overview]
Message-ID: <b0a1d728-6ef5-9cca-4cb9-18e35df61748@baylibre.com> (raw)
In-Reply-To: <20230517022557.24388-5-walter.chang@mediatek.com>
On 17/05/2023 04:25, walter.chang@mediatek.com wrote:
> Make the timer-mediatek driver which can register
> an always-on timer as tick_broadcast_device on
> MediaTek SoCs become loadable module in GKI.
Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com>
next prev parent reply other threads:[~2023-05-23 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 2:25 [PATCH v5 0/4] Support timer drivers as loadable modules walter.chang
2023-05-17 2:25 ` [PATCH v5 1/4] time/sched_clock: Export sched_clock_register() walter.chang
2024-06-07 15:03 ` Carlos Llamas
2023-05-17 2:25 ` [PATCH v5 2/4] clocksource/drivers/mmio: Export clocksource_mmio_init() walter.chang
2023-05-17 2:25 ` [PATCH v5 3/4] clocksource/drivers/timer-of: Remove __init markings walter.chang
2023-05-17 2:25 ` [PATCH v5 4/4] clocksource/drivers/timer-mediatek: Make timer-mediatek become loadable module walter.chang
2023-05-23 11:28 ` Alexandre Mergnat [this message]
2023-06-19 2:17 ` [PATCH v5 0/4] Support timer drivers as loadable modules Walter Chang (張維哲)
2023-06-19 16:44 ` Daniel Lezcano
2023-07-06 1:07 ` Walter Chang (張維哲)
2024-01-23 2:40 ` Walter Chang (張維哲)
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=b0a1d728-6ef5-9cca-4cb9-18e35df61748@baylibre.com \
--to=amergnat@baylibre.com \
--cc=Chun-hung.Wu@mediatek.com \
--cc=Freddy.Hsin@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.lezcano@linaro.org \
--cc=jstultz@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=macro@orcam.me.uk \
--cc=matthias.bgg@gmail.com \
--cc=stanley.chu@mediatek.com \
--cc=tglx@linutronix.de \
--cc=walter.chang@mediatek.com \
--cc=wsd_upstream@mediatek.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
all inboxes | Powered by JetHome®