From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-pci@vger.kernel.org
Subject: [PATCH 0/7] tree-wide: use proper 'R-Car' product name
Date: Sun, 28 May 2017 11:30:43 +0200 [thread overview]
Message-ID: <20170528093051.11816-1-wsa+renesas@sang-engineering.com> (raw)
Small series to get the R-Car product name proper. Based on
renesas-drivers/master, but can be applied to current linus/master as well.
Except for the MMC patch, which depends on mmc/next.
Please apply.
Wolfram Sang (7):
dmaengine: use proper name for the R-Car SoC
i2c: use proper name for the R-Car SoC
iio: use proper name for the R-Car SoC
mmc: use proper name for the R-Car SoC
pci: use proper name for the R-Car SoC
[media] soc_camera: rcar_vin: use proper name for the R-Car SoC
[media] v4l: rcar_fdp1: use proper name for the R-Car SoC
Documentation/devicetree/bindings/dma/shdma.txt | 2 +-
Documentation/devicetree/bindings/iio/adc/renesas,gyroadc.txt | 2 +-
Documentation/devicetree/bindings/media/rcar_vin.txt | 4 ++--
Documentation/devicetree/bindings/pci/rcar-pci.txt | 2 +-
drivers/i2c/busses/i2c-rcar.c | 2 +-
drivers/media/platform/rcar_fdp1.c | 2 +-
drivers/mmc/host/renesas_sdhi_core.c | 2 +-
include/linux/mfd/tmio.h | 2 +-
8 files changed, 9 insertions(+), 9 deletions(-)
--
2.11.0
next reply other threads:[~2017-05-28 9:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 9:30 Wolfram Sang [this message]
2017-05-28 9:30 ` [PATCH 1/7] dmaengine: use proper name for the R-Car SoC Wolfram Sang
2017-05-29 9:12 ` 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 2/7] i2c: " Wolfram Sang
2017-05-29 9:13 ` Geert Uytterhoeven
2017-06-19 14:25 ` Wolfram Sang
2017-05-28 9:30 ` [PATCH 3/7] iio: " Wolfram Sang
2017-05-29 9:11 ` Geert Uytterhoeven
2017-05-31 19:46 ` Rob Herring
2017-05-28 9:30 ` [PATCH 4/7] mmc: " Wolfram Sang
2017-05-29 9:13 ` Geert Uytterhoeven
2017-05-29 14:42 ` Ulf Hansson
2017-05-30 7:16 ` Lee Jones
2017-05-30 9:26 ` Ulf Hansson
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
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
2017-05-29 9:14 ` Geert Uytterhoeven
2017-05-31 19:47 ` Rob Herring
2017-05-28 9:30 ` [PATCH 7/7] [media] v4l: rcar_fdp1: " Wolfram Sang
2017-05-29 0:41 ` 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-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.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).