From: Nicolin Chen <nicoleotsuka@gmail.com>
To: broonie@kernel.org
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
galak@codeaurora.org
Subject: [PATCH 0/8] ASoC: fsl: Refine DT binding documents for more readability
Date: Tue, 7 Oct 2014 12:29:03 -0700 [thread overview]
Message-ID: <cover.1412708790.git.nicoleotsuka@gmail.com> (raw)
This series of patches simply add indentations and blank lines to each DT
binding documents of Freescale ASoC drivers so as to make them more clear
and readable.
@Mark Brown
Not sure if they are okay to get applied through your tree.
Otherwise, I might need to change these subjects and send
them to DT maillist only. Thank you.
Nicolin Chen (8):
ASoC: fsl_esai: Add indentation for binding doc to increase
readability
ASoC: fsl_spdif: Add indentation for binding doc to increase
readability
ASoC: fsl_sai: Add indentation for binding doc to increase readability
ASoC: eukrea-tlv320: Add indentation for binding doc to increase
readability
ASoC: imx-audmux: Add indentation for binding doc to increase
readability
ASoC: imx-sgtl5000: Add indentation for binding doc to increase
readability
ASoC: imx-spdif: Add indentation for binding doc to increase
readability
ASoC: imx-wm8962: Add indentation for binding doc to increase
readability
.../devicetree/bindings/sound/eukrea-tlv320.txt | 15 +++--
.../devicetree/bindings/sound/fsl,esai.txt | 44 ++++++++-------
.../devicetree/bindings/sound/fsl,spdif.txt | 37 ++++++------
.../devicetree/bindings/sound/fsl-sai.txt | 66 ++++++++++++++--------
.../bindings/sound/imx-audio-sgtl5000.txt | 61 +++++++++++---------
.../devicetree/bindings/sound/imx-audio-spdif.txt | 22 ++++----
.../devicetree/bindings/sound/imx-audio-wm8962.txt | 45 ++++++++-------
.../devicetree/bindings/sound/imx-audmux.txt | 22 +++++---
8 files changed, 178 insertions(+), 134 deletions(-)
--
1.9.1
next reply other threads:[~2014-10-07 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 19:29 Nicolin Chen [this message]
2014-10-07 19:29 ` [PATCH 1/8] ASoC: fsl_esai: Add indentation for binding doc to increase readability Nicolin Chen
2014-10-07 19:29 ` [PATCH 2/8] ASoC: fsl_spdif: " Nicolin Chen
2014-10-07 19:29 ` [PATCH 3/8] ASoC: fsl_sai: " Nicolin Chen
2014-10-07 19:29 ` [PATCH 4/8] ASoC: eukrea-tlv320: " Nicolin Chen
2014-10-07 19:29 ` [PATCH 5/8] ASoC: imx-audmux: " Nicolin Chen
2014-10-07 19:29 ` [PATCH 6/8] ASoC: imx-sgtl5000: " Nicolin Chen
2014-10-07 19:29 ` [PATCH 7/8] ASoC: imx-spdif: " Nicolin Chen
2014-10-07 19:29 ` [PATCH 8/8] ASoC: imx-wm8962: " Nicolin Chen
[not found] ` <cover.1412708790.git.nicoleotsuka-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-10-08 12:56 ` [PATCH 0/8] ASoC: fsl: Refine DT binding documents for more readability Mark Brown
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=cover.1412708790.git.nicoleotsuka@gmail.com \
--to=nicoleotsuka@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).