From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Igor Belwon <igor.belwon@mentallysanemainliners.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: timer: exynos4210-mct: Add samsung,exynos990-mct compatible
Date: Sun, 9 Feb 2025 12:14:28 +0100 [thread overview]
Message-ID: <9142e874-cefb-404b-8932-3e712b2d8bf0@kernel.org> (raw)
In-Reply-To: <076daca7-55e0-40d4-8ea5-93254ecd19b8@linaro.org>
On 08/01/2025 17:40, Daniel Lezcano wrote:
> On 04/01/2025 21:54, Igor Belwon wrote:
>> Add a dedicated compatible for the MCT of the Exynos 990 SoC.
>> The design for the timer is reused from previous SoCs.
>>
>> Signed-off-by: Igor Belwon <igor.belwon@mentallysanemainliners.org>
>> ---
>
> Applied patch 1/2
>
Hi Daniel,
Did this really happen? You replied month ago, but linux-next still does
not have this patch and now we got new warnings on next:
https://lore.kernel.org/all/202502070055.P29PYKEE-lkp@intel.com/
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-09 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 20:54 [PATCH 0/2] Enable CMU_PERIS and MCT for Exynos990 Igor Belwon
2025-01-04 20:54 ` [PATCH 1/2] dt-bindings: timer: exynos4210-mct: Add samsung,exynos990-mct compatible Igor Belwon
2025-01-05 9:44 ` Krzysztof Kozlowski
2025-01-08 16:40 ` Daniel Lezcano
2025-02-09 11:14 ` Krzysztof Kozlowski [this message]
2025-02-09 12:38 ` Daniel Lezcano
2025-03-25 8:14 ` [tip: timers/clocksource] " tip-bot2 for Igor Belwon
2025-01-04 20:54 ` [PATCH 2/2] arm64: dts: exynos990: Add CMU_PERIS and MCT nodes Igor Belwon
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=9142e874-cefb-404b-8932-3e712b2d8bf0@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=igor.belwon@mentallysanemainliners.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.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 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®