From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Sam Protsenko <semen.protsenko@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 2/2] arm64: platform: Enable Exynos Multi-Core Timer driver
Date: Tue, 16 Nov 2021 11:24:15 +0100 [thread overview]
Message-ID: <163705825120.25687.5616659207045424814.b4-ty@canonical.com> (raw)
In-Reply-To: <20211101193531.15078-3-semen.protsenko@linaro.org>
On Mon, 1 Nov 2021 21:35:31 +0200, Sam Protsenko wrote:
> From: Marek Szyprowski <m.szyprowski@samsung.com>
>
> Some ARM64 Exynos SoCs have MCT timer block, e.g. Exynos850 and
> Exynos5433. CLKSRC_EXYNOS_MCT option is not visible unless COMPILE_TEST
> is enabled. Select CLKSRC_EXYNOS_MCT option for ARM64 ARCH_EXYNOS like
> it's done in arch/arm/mach-exynos/Kconfig, to enable MCT timer support
> for ARM64 Exynos SoCs.
>
> [...]
Applied, thanks!
[2/2] arm64: platform: Enable Exynos Multi-Core Timer driver
commit: ddb0fc6f055d12518b724fd1ee00669e07f03b96
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
next prev parent reply other threads:[~2021-11-16 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 19:35 [PATCH 0/2] clocksource: exynos_mct: Enable MCT on ARM64 Sam Protsenko
2021-11-01 19:35 ` [PATCH 1/2] clocksource: exynos_mct: Refactor resources allocation Sam Protsenko
2021-11-16 16:00 ` Daniel Lezcano
2021-11-23 13:28 ` Sam Protsenko
2022-01-10 13:00 ` [tip: timers/core] clocksource/drivers/exynos_mct: " tip-bot2 for Marek Szyprowski
2021-11-01 19:35 ` [PATCH 2/2] arm64: platform: Enable Exynos Multi-Core Timer driver Sam Protsenko
2021-11-16 10:24 ` Krzysztof Kozlowski [this message]
2021-11-23 13:32 ` (subset) " Sam Protsenko
2021-11-23 14:33 ` Krzysztof Kozlowski
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=163705825120.25687.5616659207045424814.b4-ty@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=semen.protsenko@linaro.org \
--cc=tglx@linutronix.de \
--cc=will@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).