From: Krzysztof Kozlowski <krzk@kernel.org>
To: Johan Jonker <jbx6244@yandex.com>,
Shresth Prasad <shresthprasad7@gmail.com>,
vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, heiko@sntech.de,
sebastian.reichel@collabora.com, s.hauer@pengutronix.de,
cristian.ciocaltea@collabora.com, andy.yan@rock-chips.com
Cc: 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,
skhan@linuxfoundation.org, javier.carrasco.cruz@gmail.com
Subject: Re: [PATCH v3] dt-bindings: phy: rockchip-emmc-phy: Convert to dtschema
Date: Thu, 13 Jun 2024 12:12:27 +0200 [thread overview]
Message-ID: <9ce15b81-a8bd-4833-b15e-3e6f240dcf03@kernel.org> (raw)
In-Reply-To: <cc66cca1-33db-4f30-afcf-d256a959896b@yandex.com>
On 13/06/2024 11:44, Johan Jonker wrote:
>> ---
>
> Add ack request from phy maintainer here.
Why? What do you mean for that? Why phy maintainer needs to ack patches
he is going to take?
>
>> Changes in v3:
>> - fix `reg` in example being too long
>>
>> Tested against `rockchip/rk3399-firefly.dtb`, `rockchip/rk3399-orangepi.dtb`
>> and `rockchip/rk3399-pinebook-pro.dtb`.
>>
>> .../bindings/phy/rockchip,emmc-phy.yaml | 79 +++++++++++++++++++
>> .../bindings/phy/rockchip-emmc-phy.txt | 43 ----------
>> .../devicetree/bindings/soc/rockchip/grf.yaml | 2 +-
>> 3 files changed, 80 insertions(+), 44 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/phy/rockchip,emmc-phy.yaml
>> delete mode 100644 Documentation/devicetree/bindings/phy/rockchip-emmc-phy.txt
>>
>> diff --git a/Documentation/devicetree/bindings/phy/rockchip,emmc-phy.yaml b/Documentation/devicetree/bindings/phy/rockchip,emmc-phy.yaml
>> new file mode 100644
>> index 000000000000..85d74b343991
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/rockchip,emmc-phy.yaml
>> @@ -0,0 +1,79 @@
>
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>
> You are converting an existing document, so GPL 2 only.
Which copyrightable part was copied? This comment is not correct in
general, because conversions are dual-licensed (there are exceptions,
but that's the generic rule).
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-13 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 8:58 [PATCH v3] dt-bindings: phy: rockchip-emmc-phy: Convert to dtschema Shresth Prasad
2024-06-13 9:44 ` Johan Jonker
2024-06-13 10:12 ` Krzysztof Kozlowski [this message]
2024-06-13 10:33 ` Johan Jonker
2024-06-13 12:52 ` Krzysztof Kozlowski
2024-06-13 19:56 ` Rob Herring
2024-06-15 8:36 ` Shresth Prasad
2024-06-13 10:15 ` Krzysztof Kozlowski
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=9ce15b81-a8bd-4833-b15e-3e6f240dcf03@kernel.org \
--to=krzk@kernel.org \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jbx6244@yandex.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
--cc=shresthprasad7@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=vkoul@kernel.org \
/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).