From: Rob Herring <robh@kernel.org>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-pci@vger.kernel.org, linux-sh@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/4] PCI: rcar-gen2: add device tree support for r8a7793
Date: Fri, 4 Dec 2015 09:01:50 -0600 [thread overview]
Message-ID: <20151204150150.GA26773@rob-hp-laptop> (raw)
In-Reply-To: <1449096700-23304-3-git-send-email-horms+renesas@verge.net.au>
On Thu, Dec 03, 2015 at 07:51:38AM +0900, Simon Horman wrote:
> Simply document new compatibility string.
> As a previous patch adds a generic R-Car Gen2 compatibility string
> there appears to be no need for a driver updates.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Acked-by: Rob Herring <robh@kernel.org>
>
> ---
> * The r8a7792 is omitted from this change as the hardware in question
> does not appear to be present on that SoC.
>
> v2
> * No change
> ---
> Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt b/Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt
> index 089a99dcdf10..9c50e0c9d6da 100644
> --- a/Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt
> +++ b/Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt
> @@ -8,6 +8,7 @@ OHCI and EHCI controllers.
> Required properties:
> - compatible: "renesas,pci-r8a7790" for the R8A7790 SoC;
> "renesas,pci-r8a7791" for the R8A7791 SoC;
> + "renesas,pci-r8a7793" for the R8A7793 SoC;
> "renesas,pci-r8a7794" for the R8A7794 SoC;
> "renesas,pci-rcar-gen2" for a generic R-Car Gen2 compatible device.
>
> --
> 2.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-04 15:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 22:51 [PATCH v2 0/4] PCI: rcar, rcar-gen2: More Gen2 compatibility strings Simon Horman
2015-12-02 22:51 ` [PATCH v2 1/4] PCI: rcar-gen2: add gen2 fallback compatibility string Simon Horman
2015-12-04 15:00 ` Rob Herring
2015-12-07 15:40 ` Bjorn Helgaas
[not found] ` <1449096700-23304-1-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2015-12-02 22:51 ` [PATCH v2 2/4] PCI: rcar-gen2: add device tree support for r8a7793 Simon Horman
2015-12-04 15:01 ` Rob Herring [this message]
2015-12-02 22:51 ` [PATCH v2 3/4] PCI: rcar: add gen2 fallback compatibility string Simon Horman
2015-12-04 15:02 ` Rob Herring
2015-12-07 15:41 ` Bjorn Helgaas
2015-12-02 22:51 ` [PATCH v2 4/4] PCI: rcar: add device tree support for r8a7793 Simon Horman
2015-12-04 15:05 ` Rob Herring
2015-12-09 18:37 ` [PATCH v2 0/4] PCI: rcar, rcar-gen2: More Gen2 compatibility strings Bjorn Helgaas
2015-12-11 2:14 ` Simon Horman
2015-12-11 14:59 ` Bjorn Helgaas
2015-12-11 15:58 ` Geert Uytterhoeven
2016-02-04 22:01 ` Bjorn Helgaas
2016-02-05 7:43 ` Geert Uytterhoeven
2016-02-05 16:10 ` Bjorn Helgaas
2016-02-05 16:26 ` 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=20151204150150.GA26773@rob-hp-laptop \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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