public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Lucas Tanure <lucas.tanure@collabora.com>
Cc: Kishon Vijay Abraham I <kishon@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Krzysztof Wilczynski <kw@linux.com>,
	Bjorn Helgaas <bhelgaas@google.com>, Qu Wenruo <wqu@suse.com>,
	Piotr Oniszczuk <piotr.oniszczuk@gmail.com>,
	Peter Geis <pgwipeout@gmail.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCHv2 0/3] Add PCIe2 driver support for Rockchip
Date: Fri, 31 Mar 2023 19:25:46 +0530	[thread overview]
Message-ID: <ZCbmYqvRTRbKw8wj@matsya> (raw)
In-Reply-To: <20230314135555.44162-1-lucas.tanure@collabora.com>

On 14-03-23, 13:55, Lucas Tanure wrote:
> I am assisting with PCIe and networking bring-up for Rock Pi 5B (RK3588).
> We sent this series a few days ago:
> https://lore.kernel.org/all/20230310080518.78054-1-lucas.tanure@collabora.com/
> 
> >From that conversation we decided to send patches for Rockchip that don't
> require GIC/ITS implementation. We will send that in a separed series.
> Making easier for reviews and unblocking patches that don't require
> GIC/ITS implementation.
> 
> This is work based on prior work from XiaoDong Huang and
> Peter Geis fixing this issue specifically for Rockchip 356x.
> Plus comments of Robin Murphy about Non-Coherent properties.

Applied, thanks

-- 
~Vinod

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2023-03-31 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 13:55 [PATCHv2 0/3] Add PCIe2 driver support for Rockchip Lucas Tanure
2023-03-14 13:55 ` [PATCHv2 1/3] dt-bindings: PCI: dwc: Add rk3588 compatible Lucas Tanure
2023-03-14 14:29   ` Krzysztof Kozlowski
2023-03-14 13:55 ` [PATCHv2 2/3] dt-bindings: phy: rockchip: " Lucas Tanure
2023-03-14 13:55 ` [PATCHv2 3/3] phy: rockchip: Add naneng combo phy support for RK3588 Lucas Tanure
2023-03-31 13:55 ` Vinod Koul [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=ZCbmYqvRTRbKw8wj@matsya \
    --to=vkoul@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=kever.yang@rock-chips.com \
    --cc=kishon@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=lucas.tanure@collabora.com \
    --cc=maz@kernel.org \
    --cc=pgwipeout@gmail.com \
    --cc=piotr.oniszczuk@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wqu@suse.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