From: Tony Lindgren <tony@atomide.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Tero Kristo <t-kristo@ti.com>, Jason Yan <yanaijie@huawei.com>,
mturquette@baylibre.com, linux-omap@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH] clk: ti: dra7: remove two unused symbols
Date: Thu, 14 May 2020 13:02:19 -0700 [thread overview]
Message-ID: <20200514200219.GQ37466@atomide.com> (raw)
In-Reply-To: <158948631725.215346.11486245758636089798@swboyd.mtv.corp.google.com>
* Stephen Boyd <sboyd@kernel.org> [200514 19:59]:
> Quoting Tony Lindgren (2020-04-17 08:33:42)
> > Tero,
> >
> > * Jason Yan <yanaijie@huawei.com> [200417 07:09]:
> > > Fix the following gcc warning:
> > >
> > > drivers/clk/ti/clk-7xx.c:320:43: warning: \u2018dra7_gpu_sys_clk_data\u2019
> > > defined but not used [-Wunused-const-variable=]
> > > static const struct omap_clkctrl_div_data dra7_gpu_sys_clk_data
> > > __initconst = {
> > > ^~~~~~~~~~~~~~~~~~~~~
> > > drivers/clk/ti/clk-7xx.c:315:27: warning: \u2018dra7_gpu_sys_clk_parents\u2019
> > > defined but not used [-Wunused-const-variable=]
> > > static const char * const dra7_gpu_sys_clk_parents[] __initconst = {
> > > ^~~~~~~~~~~~~~~~~~~~~~~~
> >
> > Looks like this started happening with commit 957ad44ff5f2
> > ("clk: ti: add clkctrl data dra7 sgx") as I did it based on
> > omap5. But the clocks seem slightly different, care to check
> > sgx clocking against the TRM in case I also messed up something
> > else?
>
> Is that an ack?
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2020-05-14 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 7:35 [PATCH] clk: ti: dra7: remove two unused symbols Jason Yan
2020-04-17 15:33 ` Tony Lindgren
2020-05-14 19:58 ` Stephen Boyd
2020-05-14 20:02 ` Tony Lindgren [this message]
2020-05-27 3:24 ` 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=20200514200219.GQ37466@atomide.com \
--to=tony@atomide.com \
--cc=hulkci@huawei.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=t-kristo@ti.com \
--cc=yanaijie@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).