linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Biju Das <biju.das@bp.renesas.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Simon Horman <horms@verge.net.au>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH] dt-bindings: PCI: rcar: Add device tree support for r8a774a1
Date: Tue, 18 Jun 2019 10:38:21 +0000	[thread overview]
Message-ID: <OSBPR01MB2103F1D063171E45B4E5034DB8EA0@OSBPR01MB2103.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190614163351.GA30511@e121166-lin.cambridge.arm.com>

Hello Lorenzo and Simon,

Thanks for the feedback.

> Subject: Re: [PATCH] dt-bindings: PCI: rcar: Add device tree support for
> r8a774a1
> 
> On Wed, Jun 12, 2019 at 01:46:29PM +0200, Simon Horman wrote:
> > On Fri, Jun 07, 2019 at 08:03:36AM +0100, Biju Das wrote:
> > > Add PCIe support for the RZ/G2M (a.k.a. R8A774A1).
> > >
> > > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> >
> > Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> 
> Should I pick this up and send it via the PCI tree ?
> 
> Just let me know please, thanks.

Simon, 
What do you think ?

Regards,
Biju

> 
> > > ---
> > >  Documentation/devicetree/bindings/pci/rcar-pci.txt | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/pci/rcar-pci.txt
> b/Documentation/devicetree/bindings/pci/rcar-pci.txt
> > > index 6904882..45bba9f 100644
> > > --- a/Documentation/devicetree/bindings/pci/rcar-pci.txt
> > > +++ b/Documentation/devicetree/bindings/pci/rcar-pci.txt
> > > @@ -3,6 +3,7 @@
> > >  Required properties:
> > >  compatible: "renesas,pcie-r8a7743" for the R8A7743 SoC;
> > >  	    "renesas,pcie-r8a7744" for the R8A7744 SoC;
> > > +	    "renesas,pcie-r8a774a1" for the R8A774A1 SoC;
> > >  	    "renesas,pcie-r8a774c0" for the R8A774C0 SoC;
> > >  	    "renesas,pcie-r8a7779" for the R8A7779 SoC;
> > >  	    "renesas,pcie-r8a7790" for the R8A7790 SoC;
> > > --
> > > 2.7.4
> > >

  reply	other threads:[~2019-06-18 10:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07  7:03 [PATCH] dt-bindings: PCI: rcar: Add device tree support for r8a774a1 Biju Das
2019-06-12  7:52 ` Geert Uytterhoeven
2019-06-12 11:46 ` Simon Horman
2019-06-14 16:33   ` Lorenzo Pieralisi
2019-06-18 10:38     ` Biju Das [this message]
2019-06-19 11:48       ` Simon Horman
2019-06-21  9:58 ` Lorenzo Pieralisi

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=OSBPR01MB2103F1D063171E45B4E5034DB8EA0@OSBPR01MB2103.jpnprd01.prod.outlook.com \
    --to=biju.das@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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).