From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Marek Vasut <marex@denx.de>, devicetree@vger.kernel.org
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: rtc: m41t80: Convert text schema to YAML one
Date: Sun, 11 Dec 2022 21:27:41 +0100 [thread overview]
Message-ID: <a7894637-dee0-35dc-238f-dee222103d0e@linaro.org> (raw)
In-Reply-To: <336cf0b4-d0a7-42b9-5116-ad792b2aceb6@denx.de>
On 11/12/2022 21:26, Marek Vasut wrote:
>>> diff --git a/Documentation/devicetree/bindings/rtc/st,m41t80.yaml b/Documentation/devicetree/bindings/rtc/st,m41t80.yaml
>>> new file mode 100644
>>> index 0000000000000..9977c8954307e
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/rtc/st,m41t80.yaml
>>> @@ -0,0 +1,73 @@
>>> +# SPDX-License-Identifier: GPL-2.0
>>
>> I missed that one during previous review - why not dual license? I do
>> not see here any text (hardware description) being copied. Is it because
>> of DTS example?
>
> Copy paste from -- likely --
> Documentation/devicetree/bindings/rtc/rtc-ds1307.yaml:#
> SPDX-License-Identifier: GPL-2.0
>
> Would you prefer
>
> (GPL-2.0-only OR BSD-2-Clause)
>
> ?
Yes, please.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-12-11 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 3:00 [PATCH v2 1/2] dt-bindings: rtc: m41t80: Convert text schema to YAML one Marek Vasut
2022-12-11 3:00 ` [PATCH v2 2/2] dt-bindings: rtc: m41t80: Mark the clock: subnode as deprecated Marek Vasut
2022-12-11 20:21 ` [PATCH v2 1/2] dt-bindings: rtc: m41t80: Convert text schema to YAML one Krzysztof Kozlowski
2022-12-11 20:26 ` Marek Vasut
2022-12-11 20:27 ` Krzysztof Kozlowski [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=a7894637-dee0-35dc-238f-dee222103d0e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-rtc@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@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).