[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170508070826.GF17010@vireshk-i7>
Date: Mon, 8 May 2017 12:38:26 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Sean Wang <sean.wang@...iatek.com>
Cc: rjw@...ysocki.net, robh+dt@...nel.org, matthias.bgg@...il.com,
mark.rutland@....com, mturquette@...libre.com,
jamesjj.liao@...iatek.com, p.zabel@...gutronix.de,
shunli.wang@...iatek.com, erin.lo@...iatek.com, jdelvare@...e.de,
devicetree@...r.kernel.org, linux-mediatek@...ts.infradead.org,
linux-pm@...r.kernel.org, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/6] dt-bindings: cpufreq: move Mediatek cpufreq
dt-bindings document to proper place
On 08-05-17, 14:19, Sean Wang wrote:
> Okay, I will do it with you provided command again.
>
> What I did for the patch is just "git mv
> Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt
> Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt"
> and no any changing data in the content.
I was quite sure that you have done exactly that, but then we are
supposed to review and make sure you haven't done any mistakes.
That's where those options would make our life easier. Look at the
patch created by that command and you wouldn't see any diff at all.
--
viresh
Powered by blists - more mailing lists