devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <sean.wang@mediatek.com>
To: viresh.kumar@linaro.org, robh+dt@kernel.org,
	matthias.bgg@gmail.com, mark.rutland@arm.com,
	jamesjj.liao@mediatek.com, p.zabel@pengutronix.de,
	shunli.wang@mediatek.com, erin.lo@mediatek.com, jdelvare@suse.de,
	devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Sean Wang <sean.wang@mediatek.com>
Subject: [PATCH v4 2/3] dt-bindings: cpufreq: move MediaTek cpufreq dt-bindings document to proper place
Date: Mon, 10 Jul 2017 22:23:09 +0800	[thread overview]
Message-ID: <ff9b099839f5a83ef45771dd4fc5d72b7b807f1c.1499692967.git.sean.wang@mediatek.com> (raw)
In-Reply-To: <cover.1499692967.git.sean.wang@mediatek.com>

From: Sean Wang <sean.wang@mediatek.com>

The old place is Documentation/devicetree/bindings/clock/ that would
let people hard to find how to use MediaTek cpufreq driver, so moving
it to the appropriate place as other cpufreq drivers done would be
better.

Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
---
 .../bindings/{clock/mt8173-cpu-dvfs.txt => cpufreq/cpufreq-mediatek.txt}  | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename Documentation/devicetree/bindings/{clock/mt8173-cpu-dvfs.txt => cpufreq/cpufreq-mediatek.txt} (100%)

diff --git a/Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt
similarity index 100%
rename from Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt
rename to Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt
-- 
2.7.4

  parent reply	other threads:[~2017-07-10 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 14:23 [PATCH v4 0/3] some fixups for MediaTek cpufreq driver sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-07-10 14:23 ` [PATCH v4 1/3] cpufreq: mediatek: Add support of cpufreq to MT2701/MT7623 SoC sean.wang
     [not found]   ` <feabcfd53899954198c6620e9d9b68f4a3c55201.1499692967.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-07-11  2:49     ` Eddie Huang
2017-07-12 14:50       ` Matthias Brugger
2017-07-13  3:16         ` Viresh Kumar
2017-07-13  3:54           ` Eddie Huang
2017-07-17  8:05             ` Jean Delvare
2017-07-17  8:06     ` Jean Delvare
2017-07-10 14:23 ` sean.wang [this message]
2017-07-10 14:23 ` [PATCH v4 3/3] dt-bindings: cpufreq: enhance MediaTek cpufreq dt-binding document sean.wang
     [not found] ` <cover.1499692967.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-07-17  6:16   ` [PATCH v4 0/3] some fixups for MediaTek cpufreq driver Sean Wang
2017-07-17  7:35     ` Viresh Kumar
2017-07-17 11:33       ` Rafael J. Wysocki

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=ff9b099839f5a83ef45771dd4fc5d72b7b807f1c.1499692967.git.sean.wang@mediatek.com \
    --to=sean.wang@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=erin.lo@mediatek.com \
    --cc=jamesjj.liao@mediatek.com \
    --cc=jdelvare@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=shunli.wang@mediatek.com \
    --cc=viresh.kumar@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).