All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@linaro.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>, <pdeschrijver@nvidia.com>
Cc: Stephen Warren <swarren@nvidia.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: tegra: Implement locking for super clock
Date: Thu, 07 Feb 2013 10:57:42 -0800	[thread overview]
Message-ID: <20130207185742.11471.19037@quantum> (raw)
In-Reply-To: <1360254261-23000-1-git-send-email-pdeschrijver@nvidia.com>

Quoting Peter De Schrijver (2013-02-07 08:24:14)
> Although tegra_clk_register_super_mux() has a lock parameter, the lock is not
> actually used by the code. Fixed with this patch.
> 
> Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> ---
>  drivers/clk/tegra/clk-super.c |   18 +++++++++++++++---
>  1 files changed, 15 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/clk/tegra/clk-super.c b/drivers/clk/tegra/clk-super.c
> index 7ad48a8..2fd924d 100644
> --- a/drivers/clk/tegra/clk-super.c
> +++ b/drivers/clk/tegra/clk-super.c
> @@ -73,7 +73,12 @@ static int clk_super_set_parent(struct clk_hw *hw, u8 index)
>  {
>         struct tegra_clk_super_mux *mux = to_clk_super_mux(hw);
>         u32 val, state;
> +       int err = 0;
>         u8 parent_index, shift;
> +       unsigned long flags = 0;

I don't think initializing flags to zero is necessary but it is not a
big deal.  Is gcc throwing a warning?  Otherwise:

Acked-by: Mike Turquette <mturquette@linaro.org>

Regards,
Mike

  reply	other threads:[~2013-02-07 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 16:24 [PATCH] clk: tegra: Implement locking for super clock Peter De Schrijver
2013-02-07 18:57 ` Mike Turquette [this message]
2013-02-07 19:13   ` Stephen Warren
2013-02-08 10:16   ` Peter De Schrijver
2013-02-08  5:21 ` Prashant Gaikwad

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=20130207185742.11471.19037@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@nvidia.com \
    --cc=swarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.