From: Jeffrey Hugo <jhugo@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
andy.gross@linaro.org, david.brown@linaro.org,
mturquette@baylibre.com
Cc: bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
marc.w.gonzalez@free.fr
Subject: Re: [PATCH v2] clk: qcom: Drop unused 8998 clock
Date: Thu, 13 Dec 2018 15:32:12 -0700 [thread overview]
Message-ID: <d7ac2e27-8e9e-7ee1-430d-ed0f61d98171@codeaurora.org> (raw)
In-Reply-To: <154472988944.19322.6557891989616167911@swboyd.mtv.corp.google.com>
On 12/13/2018 12:38 PM, Stephen Boyd wrote:
> Quoting Jeffrey Hugo (2018-12-13 09:09:09)
>> gcc_lpass_trig_clk is not used downstream, therefore there is no reason to
>> expect it to be needed for clients. Let's remove it because messing with
>> the clock has been observed to cause Linux hangs when the qdss_clk is
>> initialized by rpmcc.
>>
>> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
>> Reviewed-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
>> ---
>>
>> v2:
>> -corrected commit text per Marc
>> -added Marc's reviewed-by
>
> Please slow down. There isn't any need to resend for such things.
>
Sorry. Used to other maintainers.
From your v1 comment, would be
Fixes: 4807c71cc688 (arm64: dts: Add msm8998 SoC and MTP board support)
I'm assuming from the above, you'll just apply the tag when you apply
the change.
--
Jeffrey Hugo
Qualcomm Datacenter Technologies as an affiliate of Qualcomm
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-12-13 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 17:09 [PATCH v2] clk: qcom: Drop unused 8998 clock Jeffrey Hugo
2018-12-13 19:38 ` Stephen Boyd
2018-12-13 22:32 ` Jeffrey Hugo [this message]
2018-12-14 1:32 ` Stephen Boyd
2018-12-14 21:42 ` 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=d7ac2e27-8e9e-7ee1-430d-ed0f61d98171@codeaurora.org \
--to=jhugo@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).