From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Chanwoo Choi <cwchoi00@gmail.com>, Rob Herring <robh@kernel.org>
Cc: 박경민 <kyungmin.park@samsung.com>, "Kukjin Kim" <kgene@kernel.org>,
크쉬시토프 <k.kozlowski@samsung.com>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"tjakobi@math.uni-bielefeld.de" <tjakobi@math.uni-bielefeld.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>
Subject: Re: Re: [RFC PATCH 02/15] PM / devfreq: exynos: Add documentation for generic exynos bus frequency driver
Date: Mon, 30 Nov 2015 07:23:31 +0000 (GMT) [thread overview]
Message-ID: <962403713.42381448868207072.JavaMail.weblogic@epmlwas08c> (raw)
> Hi Rob,
>
> On Sat, Nov 28, 2015 at 5:30 AM, Rob Herring <robh@kernel.org> wrote:
> > On Thu, Nov 26, 2015 at 10:47:26PM +0900, Chanwoo Choi wrote:
> >> This patch adds the documentation for generic exynos bus frequency
> >> driver.
> >>
> >> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> >> ---
> >> .../devicetree/bindings/devfreq/exynos-bus.txt | 92 ++++++++++++++++++++++
> >> 1 file changed, 92 insertions(+)
> >> create mode 100644 Documentation/devicetree/bindings/devfreq/exynos-bus.txt
> >> +Example2 :
> >> + The bus of DMC block in exynos3250.dtsi are listed below:
> >
> > What is DMC?
>
> DMC (DRAM Memory Controller)
It's Dynamic Memory Controller. (DRAM =~ Dynamic Memory)
You may need to write the full name with the first reference of DMC there
in the documentation as "DMC" may confuse a lot of people.
Cheers,
MyungJoo
reply other threads:[~2015-11-30 7:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=962403713.42381448868207072.JavaMail.weblogic@epmlwas08c \
--to=myungjoo.ham@samsung.com \
--cc=cwchoi00@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh@kernel.org \
--cc=tjakobi@math.uni-bielefeld.de \
/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).