From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: Qu Wenruo <wqu@suse.com>
Cc: "Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Peter Geis" <pgwipeout@gmail.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
"Heiko Stübner" <heiko@sntech.de>,
lucas.tanure@collabora.com
Subject: Re: [PATCH RFC 0/5] arm64: rockchip: enable PCIE3 controller and its phy for Rock5B boards
Date: Thu, 9 Mar 2023 14:00:57 +0100 [thread overview]
Message-ID: <6024BC59-B1ED-441C-97F8-73688022F899@gmail.com> (raw)
In-Reply-To: <dff133d1-6a8b-a838-4c85-a8bb16c7a742@suse.com>
> Wiadomość napisana przez Qu Wenruo <wqu@suse.com> w dniu 09.03.2023, o godz. 13:17:
>
>
>
> Awesome! I can finally get rid of the stupid out-of-tree r8125 driver.
>
> Would definitely have a good look into the patches and provide some feedbacks, just mind to share a git tree for easier reviewing?
>
>
Ah - git tree... my distro builder uses model with: mainline src + patches - so effectively i don’t have git tree for this code…
next prev parent reply other threads:[~2023-03-09 13:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 8:47 [PATCH RFC 0/5] arm64: rockchip: enable PCIE3 controller and its phy for Rock5B boards Qu Wenruo
2023-02-04 8:47 ` [PATCH RFC 1/5] drivers: phy: rockhip: remove 24M and 25M clock handling for naneng combphy Qu Wenruo
2023-02-04 8:47 ` [PATCH RFC 2/5] dt-bindings: pci: controller: add pcie controller binding for RK3588 Qu Wenruo
2023-02-06 10:43 ` Krzysztof Kozlowski
2023-02-04 8:48 ` [PATCH RFC 3/5] drivers: pci: controller: add PCIE controller driver " Qu Wenruo
2023-02-04 8:48 ` [PATCH RFC 4/5] arm64: dts: rockchip: add PCIE3 controller and phy " Qu Wenruo
2023-02-04 8:48 ` [PATCH RFC 5/5] arm64: dts: rockchip: enable PCIE3 controller and phy for Rock5B boards Qu Wenruo
2023-02-20 18:33 ` [PATCH RFC 0/5] arm64: rockchip: enable PCIE3 controller and its " Piotr Oniszczuk
[not found] ` <583D2908-ECED-4226-A6CD-683F0D5BEA71@gmail.com>
2023-02-21 0:14 ` Qu Wenruo
2023-02-21 18:03 ` Piotr Oniszczuk
2023-02-21 18:55 ` Peter Geis
2023-02-21 21:45 ` Sebastian Reichel
2023-02-21 23:39 ` Qu Wenruo
2023-02-22 1:25 ` Peter Geis
[not found] ` <A539A994-7E2C-4B51-8BAB-32AE475607DD@gmail.com>
2023-03-09 12:17 ` Qu Wenruo
2023-03-09 13:00 ` Piotr Oniszczuk [this message]
2023-03-10 0:16 ` Qu Wenruo
2023-03-10 8:09 ` Lucas Tanure
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=6024BC59-B1ED-441C-97F8-73688022F899@gmail.com \
--to=piotr.oniszczuk@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lucas.tanure@collabora.com \
--cc=pgwipeout@gmail.com \
--cc=sebastian.reichel@collabora.com \
--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;
as well as URLs for NNTP newsgroup(s).