From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Kieran Bingham <kieran@ksquared.org.uk>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 7/7] [media] v4l: rcar_fdp1: use proper name for the R-Car SoC
Date: Sun, 28 May 2017 11:30:50 +0200 [thread overview]
Message-ID: <20170528093051.11816-8-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20170528093051.11816-1-wsa+renesas@sang-engineering.com>
It is 'R-Car', not 'RCar'. 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.
drivers/media/platform/rcar_fdp1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/rcar_fdp1.c b/drivers/media/platform/rcar_fdp1.c
index 42f25d241edd7c..0da0eba9202cdd 100644
--- a/drivers/media/platform/rcar_fdp1.c
+++ b/drivers/media/platform/rcar_fdp1.c
@@ -1,5 +1,5 @@
/*
- * Renesas RCar Fine Display Processor
+ * Renesas R-Car Fine Display Processor
*
* Video format converter and frame deinterlacer device.
*
--
2.11.0
next prev parent reply other threads:[~2017-05-28 9:30 UTC|newest]
Thread overview: 11+ 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 ` [PATCH 6/7] [media] soc_camera: rcar_vin: use proper name for the R-Car SoC 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
2017-05-29 9:14 ` Geert Uytterhoeven
2017-05-31 19:47 ` Rob Herring
2017-05-28 9:30 ` Wolfram Sang [this message]
2017-05-29 0:41 ` [PATCH 7/7] [media] v4l: rcar_fdp1: " Kieran Bingham
2017-05-29 9:15 ` Geert Uytterhoeven
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-8-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=kieran@ksquared.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@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).