From: "谢致邦 (XIE Zhibang)" <Yeking@Red54.com>
To: linux-mips@linux-mips.org
Subject: [PATCH] MIPS: Loongson: Fix osc_clk_name
Date: Wed, 4 Jan 2017 21:45:33 +0800 [thread overview]
Message-ID: <20170104134533.GA20945@red54.local> (raw)
"osc_33m_clk" is already renamed to "osc_clk".
https://patchwork.kernel.org/patch/9338505/
Signed-off-by: 谢致邦 (XIE Zhibang) <Yeking@Red54.com>
---
arch/mips/loongson32/common/platform.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/loongson32/common/platform.c b/arch/mips/loongson32/common/platform.c
index beff0852..f9d877d4 100644
--- a/arch/mips/loongson32/common/platform.c
+++ b/arch/mips/loongson32/common/platform.c
@@ -82,7 +82,7 @@ void __init ls1x_rtc_set_extclk(struct platform_device *pdev)
/* CPUFreq */
static struct plat_ls1x_cpufreq ls1x_cpufreq_pdata = {
.clk_name = "cpu_clk",
- .osc_clk_name = "osc_33m_clk",
+ .osc_clk_name = "osc_clk",
.max_freq = 266 * 1000,
.min_freq = 33 * 1000,
};
--
2.11.0
next reply other threads:[~2017-01-04 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 13:45 谢致邦 (XIE Zhibang) [this message]
[not found] ` <CAJhJPsUgRDGiZ9ZMLMeo_AN9ywruk_NoFxGuF2Wpp07XoY2Vrg@mail.gmail.com>
2017-01-05 4:27 ` [PATCH] MIPS: Loongson: Fix osc_clk_name 谢致邦 (XIE Zhibang)
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=20170104134533.GA20945@red54.local \
--to=yeking@red54.com \
--cc=linux-mips@linux-mips.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