From: Stephen Boyd <sboyd@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] clk: ast2600: BCLK comes from EPLL
Date: Mon, 03 Oct 2022 14:12:18 -0700 [thread overview]
Message-ID: <20221003211220.3EC63C433D6@smtp.kernel.org> (raw)
In-Reply-To: <20220421040426.171256-1-joel@jms.id.au>
Quoting Joel Stanley (2022-04-20 21:04:26)
> This correction was made in the u-boot SDK recently. There are no
> in-tree users of this clock so the impact is minimal.
>
> Fixes: d3d04f6c330a ("clk: Add support for AST2600 SoC")
> Link: https://github.com/AspeedTech-BMC/u-boot/commit/8ad54a5ae15f27fea5e894cc2539a20d90019717
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
Applied to clk-next
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: BMC-SW@aspeedtech.com, Joel Stanley <joel@jms.id.au>,
Michael Turquette <mturquette@baylibre.com>,
Ryan Chen <ryan_chen@aspeedtech.com>
Cc: linux-aspeed@lists.ozlabs.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: ast2600: BCLK comes from EPLL
Date: Mon, 03 Oct 2022 14:12:18 -0700 [thread overview]
Message-ID: <20221003211220.3EC63C433D6@smtp.kernel.org> (raw)
In-Reply-To: <20220421040426.171256-1-joel@jms.id.au>
Quoting Joel Stanley (2022-04-20 21:04:26)
> This correction was made in the u-boot SDK recently. There are no
> in-tree users of this clock so the impact is minimal.
>
> Fixes: d3d04f6c330a ("clk: Add support for AST2600 SoC")
> Link: https://github.com/AspeedTech-BMC/u-boot/commit/8ad54a5ae15f27fea5e894cc2539a20d90019717
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
Applied to clk-next
next prev parent reply other threads:[~2022-10-03 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 4:04 [PATCH] clk: ast2600: BCLK comes from EPLL Joel Stanley
2022-04-21 4:04 ` Joel Stanley
2022-10-03 21:12 ` Stephen Boyd [this message]
2022-10-03 21:12 ` Stephen Boyd
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=20221003211220.3EC63C433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-aspeed@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.