All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Biju Das <biju.das@bp.renesas.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@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
Subject: Re: [PATCH] dt-bindings: PCI: rcar: Add device tree support for r8a7744
Date: Wed, 17 Oct 2018 11:18:29 +0200	[thread overview]
Message-ID: <20181017091829.tkorr4mdvpimfrqf@verge.net.au> (raw)
In-Reply-To: <20181012160408.GE23257@e107981-ln.cambridge.arm.com>

On Fri, Oct 12, 2018 at 05:04:08PM +0100, Lorenzo Pieralisi wrote:
> On Mon, Oct 08, 2018 at 09:34:45AM +0200, Simon Horman wrote:
> > On Thu, Oct 04, 2018 at 05:07:47PM +0100, Biju Das wrote:
> > > Add support for r8a7744. The Renesas RZ/G1N (R8A7744) PCIe controller
> > > is identical to the R-Car Gen2 family.
> > > 
> > > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> > > Reviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>
> > 
> > Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> 
> Simon, Biju,
> 
> I pulled the same binding for rcar2, I would pull this in the PCI tree
> too unless you object, please let me know.

No objection.

  parent reply	other threads:[~2018-10-17  9:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 16:07 [PATCH] dt-bindings: PCI: rcar: Add device tree support for r8a7744 Biju Das
2018-10-08  7:34 ` Simon Horman
2018-10-12 16:04   ` Lorenzo Pieralisi
2018-10-15  8:16     ` Biju Das
2018-10-15  8:16       ` Biju Das
2018-10-17  9:18     ` Simon Horman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-27 12:28 Biju Das
2018-10-01 12:56 ` Simon Horman
2018-10-04 10:34 ` 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=20181017091829.tkorr4mdvpimfrqf@verge.net.au \
    --to=horms@verge.net.au \
    --cc=Chris.Paterson2@renesas.com \
    --cc=bhelgaas@google.com \
    --cc=biju.das@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.