From: Stephen Warren <swarren@wwwdotorg.org>
To: Hiroshi Doyu <hdoyu@nvidia.com>
Cc: Prashant Gaikwad <pgaikwad@nvidia.com>,
"mturquette@linaro.org" <mturquette@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/9] clk: tegra: Add tegra specific clocks
Date: Thu, 17 Jan 2013 09:35:18 -0700 [thread overview]
Message-ID: <50F82846.2030008@wwwdotorg.org> (raw)
In-Reply-To: <20130117.070327.1625310713330263780.hdoyu@nvidia.com>
On 01/16/2013 10:03 PM, Hiroshi Doyu wrote:
> Stephen Warren <swarren@wwwdotorg.org> wrote @ Wed, 16 Jan 2013 21:11:24 +0100:
>
>>>> +static int clk_frac_div_set_rate(struct clk_hw *hw, unsigned long rate,
>>>> + unsigned long parent_rate)
>>>> +{
>>>> + struct tegra_clk_frac_div *divider = to_clk_frac_div(hw);
>>>> + int div;
>>>> + unsigned long flags = 0;
>>>
>>> nit, is "flags" not needed to initialize here?
>>
>> It avoids a compiler warning; the compiler doesn't that the if condition
>> that guards the path that uses flags is the same condition as the path
>> that initializes it. Or, it may be related to the fact that
>> spin_lock_irqsave() writes to the value through a pointer parameter, and
>> the compiler doesn't know it's an out-only parameter.
>
> It might be better to append the special comment /* GCC */[1] on that line.
>
> [1] https://lwn.net/Articles/529954/
I note that patch hasn't actually been merged though, so I think I'll
avoid doing that for now.
next prev parent reply other threads:[~2013-01-17 16:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 7:46 [PATCH v4 0/9] Migrate Tegra to common clock framework Prashant Gaikwad
2013-01-11 7:46 ` [PATCH v4 1/9] ARM: tegra: Add function to read chipid Prashant Gaikwad
2013-01-11 7:46 ` [PATCH v4 2/9] clk: tegra: Add tegra specific clocks Prashant Gaikwad
2013-01-11 11:48 ` Hiroshi Doyu
2013-01-11 21:35 ` Stephen Warren
2013-01-16 8:19 ` Hiroshi Doyu
2013-01-16 18:04 ` Stephen Warren
2013-01-14 7:28 ` Sivaram Nair
2013-01-16 12:31 ` Hiroshi Doyu
2013-01-16 18:44 ` Stephen Warren
2013-01-16 15:12 ` Hiroshi Doyu
2013-01-16 20:11 ` Stephen Warren
2013-01-17 5:03 ` Hiroshi Doyu
2013-01-17 16:35 ` Stephen Warren [this message]
2013-01-11 7:46 ` [PATCH v4 3/9] arm: tegra: Move tegra_cpu_car.h to linux/clk/tegra.h Prashant Gaikwad
2013-01-11 7:46 ` [PATCH v4 4/9] ARM: tegra: Define Tegra20 CAR binding Prashant Gaikwad
2013-01-11 7:46 ` [PATCH v4 5/9] ARM: Tegra: Define Tegra30 " Prashant Gaikwad
2013-01-16 11:28 ` Hiroshi Doyu
2013-01-16 17:30 ` Stephen Warren
2013-01-11 7:46 ` [PATCH v4 6/9] clk: tegra: add clock support for tegra20 Prashant Gaikwad
2013-01-11 20:54 ` Stephen Warren
2013-01-11 7:46 ` [PATCH v4 7/9] clk: tegra: add clock support for tegra30 Prashant Gaikwad
2013-01-11 12:17 ` Hiroshi Doyu
2013-01-11 21:40 ` Stephen Warren
2013-01-14 5:33 ` Hiroshi Doyu
2013-01-11 7:46 ` [PATCH v4 8/9] arm: tegra: Migrate to new clock code Prashant Gaikwad
2013-01-11 7:46 ` [PATCH v4 9/9] arm: tegra: Remove legacy " 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=50F82846.2030008@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=hdoyu@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 \
/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