From: Stephen Boyd <sboyd@codeaurora.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Mike Turquette <mturquette@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
Chen-Yu Tsai <wens@csie.org>,
linux-clk@vger.kernel.org
Subject: Re: [GIT PULL] Allwinner clock changes for 4.13
Date: Fri, 16 Jun 2017 14:50:36 -0700 [thread overview]
Message-ID: <20170616215036.GN20170@codeaurora.org> (raw)
In-Reply-To: <20170614192617.bsp5pjxrphlk36sk@flea.home>
On 06/14, Maxime Ripard wrote:
> Hi Mike, Stephen,
>
> Here is the patches for 4.13 for the Allwinner SoCs.
>
> In order to reduce the conflicts, this is based on the fixes tag I
> sent a PR for a few minutes ago.
>
Thanks. Pulled into clk-next. I did notice on new sparse warning
though for which I've applied this diff on top:
diff --git a/drivers/clk/sunxi-ng/ccu_mux.c b/drivers/clk/sunxi-ng/ccu_mux.c
index cfe4538304fb..312664155a54 100644
--- a/drivers/clk/sunxi-ng/ccu_mux.c
+++ b/drivers/clk/sunxi-ng/ccu_mux.c
@@ -68,7 +68,7 @@ unsigned long ccu_mux_helper_apply_prediv(struct ccu_common *common,
return parent_rate / ccu_mux_get_prediv(common, cm, parent_index);
}
-unsigned long ccu_mux_helper_unapply_prediv(struct ccu_common *common,
+static unsigned long ccu_mux_helper_unapply_prediv(struct ccu_common *common,
struct ccu_mux_internal *cm,
int parent_index,
unsigned long parent_rate)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner clock changes for 4.13
Date: Fri, 16 Jun 2017 14:50:36 -0700 [thread overview]
Message-ID: <20170616215036.GN20170@codeaurora.org> (raw)
In-Reply-To: <20170614192617.bsp5pjxrphlk36sk@flea.home>
On 06/14, Maxime Ripard wrote:
> Hi Mike, Stephen,
>
> Here is the patches for 4.13 for the Allwinner SoCs.
>
> In order to reduce the conflicts, this is based on the fixes tag I
> sent a PR for a few minutes ago.
>
Thanks. Pulled into clk-next. I did notice on new sparse warning
though for which I've applied this diff on top:
diff --git a/drivers/clk/sunxi-ng/ccu_mux.c b/drivers/clk/sunxi-ng/ccu_mux.c
index cfe4538304fb..312664155a54 100644
--- a/drivers/clk/sunxi-ng/ccu_mux.c
+++ b/drivers/clk/sunxi-ng/ccu_mux.c
@@ -68,7 +68,7 @@ unsigned long ccu_mux_helper_apply_prediv(struct ccu_common *common,
return parent_rate / ccu_mux_get_prediv(common, cm, parent_index);
}
-unsigned long ccu_mux_helper_unapply_prediv(struct ccu_common *common,
+static unsigned long ccu_mux_helper_unapply_prediv(struct ccu_common *common,
struct ccu_mux_internal *cm,
int parent_index,
unsigned long parent_rate)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-16 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 19:26 [GIT PULL] Allwinner clock changes for 4.13 Maxime Ripard
2017-06-14 19:26 ` Maxime Ripard
2017-06-16 21:50 ` Stephen Boyd [this message]
2017-06-16 21:50 ` Stephen Boyd
2017-06-20 6:30 ` Maxime Ripard
2017-06-20 6:30 ` Maxime Ripard
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=20170616215036.GN20170@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=wens@csie.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.