From: Bjorn Helgaas <helgaas@kernel.org>
To: Simon Xue <xxm@rock-chips.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-pci@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
Johan Jonker <jbx6244@gmail.com>,
Heiko Stuebner <heiko@sntech.de>,
Peter Geis <pgwipeout@gmail.com>,
Kever Yang <kever.yang@rock-chips.com>,
Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v10] PCI: rockchip: Add Rockchip RK356X host controller driver
Date: Thu, 24 Jun 2021 13:07:23 -0500 [thread overview]
Message-ID: <20210624180723.GA3543267@bjorn-Precision-5520> (raw)
In-Reply-To: <20210624021548.447301-1-xxm@rock-chips.com>
This needs a new driver name. We already have a "rockchip" driver
(drivers/pci/controller/pcie-rockchip-host.c) and this one needs a
different name that we can use in the subject line and similar places,
e.g., something like:
PCI: rockchip-dwc:
Using "rockchip" for the other driver might have been a mistake. We
should probably use something a little more specific for this driver
to leave room for Rockchip to produce future hardware that may require
a *third* driver.
On Thu, Jun 24, 2021 at 10:15:47AM +0800, Simon Xue wrote:
> Add a driver for the DesignWare-based PCIe controller found on
> RK356X. The existing pcie-rockchip-host driver is only used for
> the Rockchip-designed IP found on RK3399.
prev parent reply other threads:[~2021-06-24 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 2:15 [PATCH v10] PCI: rockchip: Add Rockchip RK356X host controller driver Simon Xue
2021-06-24 18:07 ` Bjorn Helgaas [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=20210624180723.GA3543267@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=xxm@rock-chips.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