From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Vinod Koul <vinod.koul@intel.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/7] dmaengine: use proper name for the R-Car SoC
Date: Sun, 28 May 2017 11:30:44 +0200 [thread overview]
Message-ID: <20170528093051.11816-2-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20170528093051.11816-1-wsa+renesas@sang-engineering.com>
It is 'R-Car', not 'r-car'. No code or binding changes, only descriptive text.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
I suggest this trivial patch should be picked individually per susbsystem.
Documentation/devicetree/bindings/dma/shdma.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/dma/shdma.txt b/Documentation/devicetree/bindings/dma/shdma.txt
index 2a3f3b8946b998..a91920a49433c2 100644
--- a/Documentation/devicetree/bindings/dma/shdma.txt
+++ b/Documentation/devicetree/bindings/dma/shdma.txt
@@ -1,6 +1,6 @@
* SHDMA Device Tree bindings
-Sh-/r-mobile and r-car systems often have multiple identical DMA controller
+Sh-/r-mobile and R-Car systems often have multiple identical DMA controller
instances, capable of serving any of a common set of DMA slave devices, using
the same configuration. To describe this topology we require all compatible
SHDMA DT nodes to be placed under a DMA multiplexer node. All such compatible
--
2.11.0
next prev parent reply other threads:[~2017-05-28 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 9:30 [PATCH 0/7] tree-wide: use proper 'R-Car' product name Wolfram Sang
2017-05-28 9:30 ` Wolfram Sang [this message]
2017-05-29 9:12 ` [PATCH 1/7] dmaengine: use proper name for the R-Car SoC Geert Uytterhoeven
2017-05-29 12:03 ` Wolfram Sang
2017-05-31 19:45 ` Rob Herring
2017-06-01 16:37 ` Vinod Koul
2017-05-28 9:30 ` [PATCH 3/7] iio: " Wolfram Sang
[not found] ` <20170528093051.11816-4-wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.org>
2017-05-29 9:11 ` Geert Uytterhoeven
2017-05-31 19:46 ` Rob Herring
2017-05-28 9:30 ` [PATCH 5/7] pci: " Wolfram Sang
2017-05-29 9:13 ` Geert Uytterhoeven
2017-05-30 8:41 ` Simon Horman
2017-05-30 21:39 ` Bjorn Helgaas
[not found] ` <20170528093051.11816-1-wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.org>
2017-05-28 9:30 ` [PATCH 6/7] [media] soc_camera: rcar_vin: " Wolfram Sang
2017-05-29 8:41 ` Sergei Shtylyov
2017-05-29 12:02 ` Wolfram Sang
2017-06-08 11:27 ` Mauro Carvalho Chehab
2017-06-08 13:57 ` Wolfram Sang
[not found] ` <20170528093051.11816-7-wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.org>
2017-05-29 9:14 ` Geert Uytterhoeven
2017-05-31 19:47 ` Rob Herring
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=20170528093051.11816-2-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vinod.koul@intel.com \
/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).