From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"mturquette@linaro.org" <mturquette@linaro.org>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] clk: tegra: override bits for Tegra114 PLLM
Date: Thu, 6 Jun 2013 11:15:42 +0300 [thread overview]
Message-ID: <20130606081542.GS3847@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <51AF5FCE.6090501@wwwdotorg.org>
On Wed, Jun 05, 2013 at 05:57:02PM +0200, Stephen Warren wrote:
> On 06/05/2013 08:08 AM, Peter De Schrijver wrote:
>
> Commit description?
>
> > diff --git a/drivers/clk/tegra/clk-tegra114.c b/drivers/clk/tegra/clk-tegra114.c
>
> > +#ifdef CONFIG_PM_SLEEP
> > +static struct cpu_clk_suspend_context {
> > + u32 clk_csite_src;
> > +} tegra114_cpu_clk_sctx;
> > +#endif
>
> That generates:
>
> drivers/clk/tegra/clk-tegra114.c:263:3: warning: ‘tegra114_cpu_clk_sctx’
> defined but not used [-Wunused-variable]
Ah. This should not be part of this patch indeed...
Cheers,
Peter.
next prev parent reply other threads:[~2013-06-06 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 14:08 [PATCH 0/4] Override bits for PLLM Peter De Schrijver
2013-06-05 14:08 ` [PATCH 1/4] clk: tegra: Add fields for override bits Peter De Schrijver
2013-06-05 14:08 ` [PATCH 2/4] clk: tegra: override bits for Tegra114 PLLM Peter De Schrijver
2013-06-05 15:57 ` Stephen Warren
2013-06-06 8:15 ` Peter De Schrijver [this message]
2013-06-05 14:08 ` [PATCH 3/4] clk: tegra: override bits for Tegra30 PLLM Peter De Schrijver
2013-06-05 14:08 ` [PATCH 4/4] clk: tegra: Use override bits when needed Peter De Schrijver
2013-06-05 14:18 ` [PATCH 0/4] Override bits for PLLM Peter De Schrijver
2013-06-05 16:29 ` Stephen Warren
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=20130606081542.GS3847@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pgaikwad@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®