devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kw@linux.com>
To: Simon Xue <xxm@rock-chips.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	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>
Subject: Re: [PATCH v4 1/2] dt-bindings: rockchip: Add DesignWare based PCIe controller
Date: Mon, 22 Feb 2021 03:37:59 +0100	[thread overview]
Message-ID: <YDMZB94qMkpOx38Q@rocinante> (raw)
In-Reply-To: <20210127022406.820975-1-xxm@rock-chips.com>

Hi Simon,

[...]
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)

The driver is only based on GPL v2.0, should this be the same, or is
there a reason for dual-license?

[...]
> +title: DesignWare based PCIe RC controller on Rockchip SoCs
[...]

What does the "RC" here stands for?  Would it be "Rockchip"?  If so,
then perhaps dropping it would be fine to do, as rest of the title
mentions "Rockchip SoCs"."  What do you think?

Krzysztof

  parent reply	other threads:[~2021-02-22  2:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  2:24 [PATCH v4 1/2] dt-bindings: rockchip: Add DesignWare based PCIe controller Simon Xue
2021-01-27  2:25 ` [PATCH v4 2/2] PCI: rockchip: add " Simon Xue
2021-02-22  0:59   ` xxm
2021-02-22  2:28   ` Krzysztof Wilczyński
2021-02-22  4:52     ` [PATCH v4 2/2] PCI: rockchip: add DesignWare based PCIe controller【请注意,邮件由kswilczynski@gmail.com代发】 xxm
2021-02-22  0:59 ` [PATCH v4 1/2] dt-bindings: rockchip: Add DesignWare based PCIe controller xxm
2021-02-22  2:37 ` Krzysztof Wilczyński [this message]
2021-02-22  4:19   ` [PATCH v4 1/2] dt-bindings: rockchip: Add DesignWare based PCIe controller【请注意,邮件由kswilczynski@gmail.com代发】 xxm

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=YDMZB94qMkpOx38Q@rocinante \
    --to=kw@linux.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=helgaas@kernel.org \
    --cc=jbx6244@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=robh+dt@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).