From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tushar Behera <tushar.behera@linaro.org>,
Mike Turquette <mturquette@linaro.org>,
Sachin Kamat <sachin.kamat@linaro.org>
Subject: linux-next: manual merge of the samsung tree with Linus' tree
Date: Thu, 20 Jun 2013 17:36:04 +1000 [thread overview]
Message-ID: <20130620173604.67b07fa0932dac4a75583fd5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
Hi Kukjin,
Today's linux-next merge of the samsung tree got a conflict in
drivers/clk/samsung/clk-exynos5250.c between commit 39b72d89eb2b ("clk:
exynos5250: Update cpufreq related clocks for EXYNOS5250") from Linus'
tree and commit 407e8d62fa7d ("clk: exynos5250: Staticize local symbols")
from the samsung tree.
I fixed it up (see below) and can carry the fix as necessary (no action
is required).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
diff --cc drivers/clk/samsung/clk-exynos5250.c
index 22d7699,f6e3031..0000000
--- a/drivers/clk/samsung/clk-exynos5250.c
+++ b/drivers/clk/samsung/clk-exynos5250.c
@@@ -207,11 -213,11 +213,11 @@@ static struct samsung_fixed_factor_cloc
FFACTOR(none, "fout_bplldiv2", "fout_bpll", 1, 2, 0),
};
- struct samsung_mux_clock exynos5250_mux_clks[] __initdata = {
+ static struct samsung_mux_clock exynos5250_mux_clks[] __initdata = {
- MUX(none, "mout_apll", mout_apll_p, SRC_CPU, 0, 1),
- MUX(none, "mout_cpu", mout_cpu_p, SRC_CPU, 16, 1),
+ MUX_A(none, "mout_apll", mout_apll_p, SRC_CPU, 0, 1, "mout_apll"),
+ MUX_A(none, "mout_cpu", mout_cpu_p, SRC_CPU, 16, 1, "mout_cpu"),
MUX(none, "mout_mpll_fout", mout_mpll_fout_p, PLL_DIV2_SEL, 4, 1),
- MUX(none, "sclk_mpll", mout_mpll_p, SRC_CORE1, 8, 1),
+ MUX_A(none, "sclk_mpll", mout_mpll_p, SRC_CORE1, 8, 1, "mout_mpll"),
MUX(none, "mout_bpll_fout", mout_bpll_fout_p, PLL_DIV2_SEL, 0, 1),
MUX(none, "sclk_bpll", mout_bpll_p, SRC_CDREX, 0, 1),
MUX(none, "mout_vpllsrc", mout_vpllsrc_p, SRC_TOP2, 0, 1),
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-06-20 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 7:36 Stephen Rothwell [this message]
2014-06-12 0:43 Stephen Rothwell
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=20130620173604.67b07fa0932dac4a75583fd5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sachin.kamat@linaro.org \
--cc=tushar.behera@linaro.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
all inboxes | Powered by JetHome®