[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <525D9A85.40102@wwwdotorg.org>
Date: Tue, 15 Oct 2013 13:41:57 -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 14/19] clk: tegra30: replace enum by binding header
On 10/15/2013 08:52 AM, Peter De Schrijver wrote:
> As the clock IDs are now specified in a header file, we can use those
> definitions instead of maintaining an internal enum.
Nit: The patch subject should say "clk: tegra:" not "clk: tegra20:" so
that anyone looking at the tags in the subject has only one "tegra"
value to look at, not a whole bunch of them.
Would it make sense to squash patches 15, 16, 18 together (and similar
for Tegra30) to avoid some churn i.e. the fact that the entire body of
tegra_periph_clk_list[] gets replaced twice?
--
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