linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Yuya Hamamachi <yuya.hamamachi.sx@renesas.com>
Cc: linux-pci <linux-pci@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: renesas: r8a77951: Add PCIe EP nodes
Date: Thu, 26 Nov 2020 12:43:56 +0100	[thread overview]
Message-ID: <CAMuHMdXY5gO=xOvqstUyCje=Et1MjvS5MjkDdL0u0HqDjURxQw@mail.gmail.com> (raw)
In-Reply-To: <20201125073303.19057-3-yuya.hamamachi.sx@renesas.com>

On Wed, Nov 25, 2020 at 8:43 AM Yuya Hamamachi
<yuya.hamamachi.sx@renesas.com> wrote:
> Add PCIe EP nodes for R8A77951 SoC dtsi.
>
> Signed-off-by: Yuya Hamamachi <yuya.hamamachi.sx@renesas.com>

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-devel for v5.11.

Gr{oetje,eeting}s,

                        Geert


--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      parent reply	other threads:[~2020-11-26 11:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201125073303.19057-1-yuya.hamamachi.sx@renesas.com>
     [not found] ` <20201125073303.19057-2-yuya.hamamachi.sx@renesas.com>
2020-11-26 10:51   ` [PATCH 1/2] dt-bindings: pci: rcar-pci-ep: Document r8a7795 Geert Uytterhoeven
     [not found] ` <20201125073303.19057-3-yuya.hamamachi.sx@renesas.com>
2020-11-26 11:43   ` Geert Uytterhoeven [this message]

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='CAMuHMdXY5gO=xOvqstUyCje=Et1MjvS5MjkDdL0u0HqDjURxQw@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --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=yuya.hamamachi.sx@renesas.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;
as well as URLs for NNTP newsgroup(s).