From: "Minkyu Kang" <mk7.kang@samsung.com>
To: <u-boot@lists.denx.de>, <trini@konsulko.com>
Cc: <promsoft@gmail.com>
Subject: Please pull u-boot-samsung master
Date: Thu, 4 Apr 2024 17:54:10 +0900 [thread overview]
Message-ID: <1ff501da866d$a93e2370$fbba6a50$@samsung.com> (raw)
In-Reply-To: CGME20240404085411epcas1p3f10e648bd35670e090592cb4fbb97d58@epcas1p3.samsung.com
Dear Tom,
The following changes since commit dde373bde392c38649c8c4420e0c98ef8d38d9dc:
Prepare v2024.04-rc5 (2024-03-25 21:56:50 -0400)
are available in the git repository at:
git@source.denx.de:u-boot/custodians/u-boot-samsung.git master
for you to fetch changes up to 1751ba9a3b79ea5083ff5c4de58fe3bd9588f32a:
clk: exynos: Add CMU_CORE and CMU_HSI for Exynos850 (2024-03-26 18:56:55
+0900)
----------------------------------------------------------------
Sam Protsenko (4):
clk: exynos: Re-arrange clocks in Exynos850 CMU_TOP
clk: exynos: Don't expose prototypes for not used functions
clk: exynos: Fix incorrect clock lookup for non-top CMUs
clk: exynos: Add CMU_CORE and CMU_HSI for Exynos850
drivers/clk/exynos/clk-exynos850.c | 326
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------
drivers/clk/exynos/clk-pll.c | 6 +-
drivers/clk/exynos/clk-pll.h | 6 ++
drivers/clk/exynos/clk.c | 47 ++++++----
drivers/clk/exynos/clk.h | 70 ++++++++++-----
5 files changed, 384 insertions(+), 71 deletions(-)
Thanks,
Minkyu Kang.
next parent reply other threads:[~2024-04-04 8:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240404085411epcas1p3f10e648bd35670e090592cb4fbb97d58@epcas1p3.samsung.com>
2024-04-04 8:54 ` Minkyu Kang [this message]
2024-04-06 0:41 ` Please pull u-boot-samsung master Tom Rini
[not found] <CGME20260225075234epcas1p4b0561d04c012cbe3574755cc475c34fe@epcas1p4.samsung.com>
2026-02-25 7:52 ` please " Minkyu Kang
2026-02-25 17:26 ` Tom Rini
[not found] <CGME20260223103749epcas1p2d9af2576eb9704b70a8572f7ccb8080f@epcas1p2.samsung.com>
2026-02-23 10:37 ` Minkyu Kang
2026-02-23 18:45 ` Tom Rini
2026-02-24 1:06 ` Minkyu Kang
2026-02-24 15:45 ` Kaustabh Chakraborty
[not found] <CGME20251202065932epcas1p317a2fa75a3b16a4984a0c0bdf0515b5a@epcas1p3.samsung.com>
2025-12-02 6:59 ` Minkyu Kang
2025-12-02 19:30 ` Tom Rini
2025-09-05 6:39 Minkyu Kang
2025-09-05 16:44 ` Tom Rini
[not found] <CGME20250725073112epcas1p364a18714ffddd807ea6c1fd1b8b373bd@epcas1p3.samsung.com>
2025-07-25 7:31 ` Please " Minkyu Kang
2025-07-25 16:31 ` Tom Rini
[not found] <CGME20250210043511epcas1p33ed93b581644b1a1a14a8710afeaaf97@epcas1p3.samsung.com>
2025-02-10 4:35 ` Minkyu Kang
2025-02-10 15:52 ` Tom Rini
[not found] <CGME20241203063944epcas1p45e5c757403cd06ebd265a93e7fdbbeff@epcas1p4.samsung.com>
2024-12-03 6:39 ` Minkyu Kang
2024-12-03 19:57 ` Tom Rini
[not found] <CGME20240822102010epcas1p434e5a447b002e8bdea5423a034c2e444@epcas1p4.samsung.com>
2024-08-22 10:20 ` Minkyu Kang
2024-08-22 21:54 ` Tom Rini
2024-08-23 7:50 ` Minkyu Kang
[not found] <CGME20240603060854epcas1p207233f59828c47f31e941894634b9af7@epcas1p2.samsung.com>
2024-06-03 6:08 ` Minkyu Kang
2024-06-03 17:42 ` Tom Rini
[not found] <CGME20240220042544epcas1p1814450956381663117a9e274d775a952@epcas1p1.samsung.com>
2024-02-20 4:25 ` Minkyu Kang
2024-02-20 18:15 ` Tom Rini
[not found] <CGME20240109015516epcas1p368e48c6d3e2433577bf7d0684966c45b@epcas1p3.samsung.com>
2024-01-09 1:55 ` Minkyu Kang
2024-01-09 15:59 ` Tom Rini
[not found] ` <29757fea-207b-53c8-844f-e76829cf04b3@posteo.net>
[not found] ` <20240111175723.GK1610741@bill-the-cat>
2024-01-12 18:52 ` Stefan Bosch
2024-01-12 18:54 ` Tom Rini
2024-01-09 17:49 ` Tom Rini
2024-01-11 5:25 ` Minkyu Kang
[not found] <CGME20231128031606epcas1p4a03b83245075b91119b523dda9899537@epcas1p4.samsung.com>
2023-11-28 3:16 ` Minkyu Kang
2023-11-28 16:28 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2021-01-22 7:45 please " Minkyu Kang
2021-01-23 17:45 ` Tom Rini
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='1ff501da866d$a93e2370$fbba6a50$@samsung.com' \
--to=mk7.kang@samsung.com \
--cc=promsoft@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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