From: Bjorn Helgaas <helgaas@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] pci: use proper name for the R-Car SoC
Date: Tue, 30 May 2017 16:39:08 -0500 [thread overview]
Message-ID: <20170530213908.GD14896@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20170528093051.11816-6-wsa+renesas@sang-engineering.com>
On Sun, May 28, 2017 at 11:30:48AM +0200, Wolfram Sang wrote:
> 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.
>
> Documentation/devicetree/bindings/pci/rcar-pci.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied with Geert and Simon's acks to pci/host-rcar for v4.13, thanks!
>
> diff --git a/Documentation/devicetree/bindings/pci/rcar-pci.txt b/Documentation/devicetree/bindings/pci/rcar-pci.txt
> index 34712d6fd25376..bd27428dda619d 100644
> --- a/Documentation/devicetree/bindings/pci/rcar-pci.txt
> +++ b/Documentation/devicetree/bindings/pci/rcar-pci.txt
> @@ -1,4 +1,4 @@
> -* Renesas RCar PCIe interface
> +* Renesas R-Car PCIe interface
>
> Required properties:
> compatible: "renesas,pcie-r8a7779" for the R8A7779 SoC;
> --
> 2.11.0
>
next prev parent reply other threads:[~2017-05-30 21:39 UTC|newest]
Thread overview: 31+ 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 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 [this message]
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=20170530213908.GD14896@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®