From: Sean Anderson <seanga2@gmail.com>
To: Tom Rini <trini@konsulko.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Michal Suchanek <msuchanek@suse.de>,
Patrick Delaunay <patrick.delaunay@foss.st.com>
Subject: Re: [GIT PULL] clk changes for v2023.01
Date: Sat, 21 Jan 2023 13:21:14 -0500 [thread overview]
Message-ID: <93cd3130-05af-59a3-c13d-9ccbd6c9ffc5@gmail.com> (raw)
In-Reply-To: <72ef21f5-4ed5-06e9-76f6-9db8156e4c98@gmail.com>
On 1/21/23 13:20, Sean Anderson wrote:
> The following changes since commit d3ccdc0fce206c1d54fbdc607333de6184e19e75:
>
> Merge tag 'efi-2022-10-rc6' of https://source.denx.de/u-boot/custodians/u-boot-efi (2022-09-30 08:30:38 -0400)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-clk.git tags/clk-2023.01
>
> for you to fetch changes up to 19fb40a5e7ee815a703ffdcc7c0fdb7933762256:
>
> clk: update clk_clean_rate_cache to use private clk struct (2022-10-19 12:28:30 -0400)
>
> ----------------------------------------------------------------
> Clock patches for 2023.01
>
> This contains various fixes (some long overdue) for the next release.
>
> ----------------------------------------------------------------
> Michal Suchanek (2):
> clk: change return type of clk_get_parent_rate from long long to ulong
> rockchip: clk: pll: Fix constant typo
>
> Patrick Delaunay (1):
> clk: update clk_clean_rate_cache to use private clk struct
>
> drivers/clk/clk-uclass.c | 20 ++++++++++++++++++--
> drivers/clk/rockchip/clk_pll.c | 6 +++---
> include/clk.h | 4 ++--
> 3 files changed, 23 insertions(+), 7 deletions(-)
Please disregard this. I fatfingered the email.
--Sean
next parent reply other threads:[~2023-01-21 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <72ef21f5-4ed5-06e9-76f6-9db8156e4c98@gmail.com>
2023-01-21 18:21 ` Sean Anderson [this message]
2022-10-19 23:56 [GIT PULL] clk changes for v2023.01 Sean Anderson
2022-10-20 19:02 ` 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=93cd3130-05af-59a3-c13d-9ccbd6c9ffc5@gmail.com \
--to=seanga2@gmail.com \
--cc=msuchanek@suse.de \
--cc=patrick.delaunay@foss.st.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