From: Stephen Boyd <sboyd@codeaurora.org>
To: Hai Li <hali@codeaurora.org>
Cc: mturquette@baylibre.com, georgi.djakov@linaro.org,
tomeu.vizoso@collabora.com, architt@codeaurora.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] clk: qcom: Use parent rate when set rate to pixel RCG clock
Date: Mon, 06 Jul 2015 12:32:14 -0700 [thread overview]
Message-ID: <559AD7BE.3090402@codeaurora.org> (raw)
In-Reply-To: <1436194176-17701-1-git-send-email-hali@codeaurora.org>
On 07/06/2015 07:49 AM, Hai Li wrote:
> Since the parent rate has been recalculated, pixel RCG clock
> should rely on it to find the correct M/N values during set_rate,
> instead of calling __clk_round_rate() to its parent again.
>
> v2: Rebase on clk-next and avoid build warning
>
> Signed-off-by: Hai Li <hali@codeaurora.org>
> Tested-by: Archit Taneja <architt@codeaurora.org>
> Fixes: 99cbd064b059 ("clk: qcom: Support display RCG clocks")
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
Huh? I didn't sign this off. The original patch was already applied, so
a new patch on top of the patch in -next that removed the index and
parent lines and renamed the variable should have been sent. Then we
have the option of applying the new patch on top to silence the warning,
or to squash it into the original patch if we want to redo clk-fixes.
I've opted to redo clk-fixes this time.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-07-06 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1435271733-24455-1-git-send-email-hali@codeaurora.org>
2015-07-06 14:49 ` [PATCH v2] clk: qcom: Use parent rate when set rate to pixel RCG clock Hai Li
2015-07-06 19:32 ` Stephen Boyd [this message]
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=559AD7BE.3090402@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=architt@codeaurora.org \
--cc=georgi.djakov@linaro.org \
--cc=hali@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=tomeu.vizoso@collabora.com \
/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;
as well as URLs for NNTP newsgroup(s).