From: Stephen Boyd <sboyd@kernel.org>
To: YueHaibing <yuehaibing@huawei.com>,
agross@kernel.org, mturquette@baylibre.com
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-msm@vger.kernel.org, YueHaibing <yuehaibing@huawei.com>
Subject: Re: [PATCH -next] clk: qcom: clk-rpm: remove unused code
Date: Fri, 16 Aug 2019 10:35:12 -0700 [thread overview]
Message-ID: <20190816173513.7D0C32086C@mail.kernel.org> (raw)
In-Reply-To: <20190816135944.54232-1-yuehaibing@huawei.com>
Quoting YueHaibing (2019-08-16 06:59:44)
> drivers/clk/qcom/clk-rpm.c:453:29: warning:
> clk_rpm_branch_ops defined but not used [-Wunused-const-variable=]
>
> It is never used, also the macros 'DEFINE_CLK_RPM_CXO_BRANCH'
> and 'DEFINE_CLK_RPM_CXO_BRANCH' are unused, so remove them.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
Sorry, apparently we're leaving this code around for qcom folks to use
one day.
prev parent reply other threads:[~2019-08-16 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 13:59 [PATCH -next] clk: qcom: clk-rpm: remove unused code YueHaibing
2019-08-16 17:35 ` 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=20190816173513.7D0C32086C@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=yuehaibing@huawei.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).