From: Rob Herring <robh@kernel.org>
To: Siarhei Volkau <lis8215@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Cercueil <paul@crapouillou.net>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 3/4] dt-bindings: clock: Add Ingenic JZ4755 CGU header
Date: Mon, 17 Oct 2022 13:34:53 -0500 [thread overview]
Message-ID: <20221017183453.GA2253413-robh@kernel.org> (raw)
In-Reply-To: <CAKNVLfZ8qi4MS6ineF4M5xnSmHW+=P5mdgifmr74g4kOSK2wGA@mail.gmail.com>
On Sun, Oct 16, 2022 at 09:21:18PM +0300, Siarhei Volkau wrote:
> вс, 16 окт. 2022 г. в 18:32, Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org>:
>
> > Why did you choose 2.0+?
>
> It's the first time that I need to choose a license, so it's a bit
> confusing what
> side effects they have, especially in that particular case.
>
> What do you recommend?
Are you fine with GPLv4, GPLv5? Considering they haven't been written, I
wouldn't be.
Rob
next prev parent reply other threads:[~2022-10-17 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 15:01 [PATCH v2 0/4] Add Ingenic JZ4755 CGU driver Siarhei Volkau
2022-10-16 15:01 ` [PATCH v2 1/4] MIPS: ingenic: add new machine type MACH_JZ4755 Siarhei Volkau
2022-10-17 9:09 ` Paul Cercueil
2022-10-17 16:40 ` Siarhei Volkau
2022-10-16 15:01 ` [PATCH v2 2/4] dt-bindings: ingenic: Add support for the JZ4755 CGU Siarhei Volkau
2022-10-16 15:31 ` Krzysztof Kozlowski
2022-10-16 15:01 ` [PATCH v2 3/4] dt-bindings: clock: Add Ingenic JZ4755 CGU header Siarhei Volkau
2022-10-16 15:32 ` Krzysztof Kozlowski
2022-10-16 18:21 ` Siarhei Volkau
2022-10-17 1:00 ` Krzysztof Kozlowski
2022-10-17 18:34 ` Rob Herring [this message]
2022-10-16 15:01 ` [PATCH v2 4/4] clk: Add Ingenic JZ4755 CGU driver Siarhei Volkau
2022-10-17 9:24 ` Paul Cercueil
2022-10-17 17:10 ` Siarhei Volkau
2022-10-17 17:24 ` Paul Cercueil
2022-10-17 18:07 ` Siarhei Volkau
2022-10-18 13:30 ` Paul Cercueil
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=20221017183453.GA2253413-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lis8215@gmail.com \
--cc=mturquette@baylibre.com \
--cc=paul@crapouillou.net \
--cc=sboyd@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).