[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <525D9117.9050009@wwwdotorg.org>
Date: Tue, 15 Oct 2013 13:01:43 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: Peter De Schrijver <pdeschrijver@...dia.com>
CC: Prashant Gaikwad <pgaikwad@...dia.com>,
Mike Turquette <mturquette@...aro.org>,
Thierry Reding <thierry.reding@...il.com>,
Rob Herring <rob.herring@...xeda.com>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Hiroshi Doyu <hdoyu@...dia.com>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v3 08/19] clk: tegra: add common infra for DT clocks
On 10/15/2013 08:52 AM, Peter De Schrijver wrote:
> Introduce a common infrastructure for sharing clock initialization between
> SoCs.
> diff --git a/drivers/clk/tegra/clk.c b/drivers/clk/tegra/clk.c
> +struct clk ** __init tegra_lookup_dt_id(int clk_id,
> + struct tegra_clk *tegra_clk)
> +{
> + if (tegra_clk[clk_id].present)
> + return &clks[tegra_clk[clk_id].dt_id];
> + else
> + return NULL;
Does this need range-checking? Or do we assume that since this is an
internal function, "clk_id" will never be out-of-range?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists