Rob Herring <robh@xxxxxxxxxx> napsal Čt, 6. úno 2020 v 14∶27:
On Thu, Feb 6, 2020 at 2:16 PM David Heidelberg <david@xxxxxxx> wrote:
Rob Herring <robh@xxxxxxxxxx> napsal Čt, 6. úno 2020 v 19∶07:
> On Tue, Feb 04, 2020 at 10:30:27AM +0100, David Heidelberg wrote:
>> This commit add dt-bindings support to al3320a driver and
>> vendor-prefix
>> dynaimage.
>>
>>
>> Signed-off-by: David Heidelberg <david@xxxxxxx>
>> ---
>> .../bindings/iio/light/al3320a.yaml | 45
>> +++++++++++++++++++
>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>> 2 files changed, 47 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/iio/light/al3320a.yaml
>>
>> diff --git
>> a/Documentation/devicetree/bindings/iio/light/al3320a.yaml
>> b/Documentation/devicetree/bindings/iio/light/al3320a.yaml
>> new file mode 100644
>> index 000000000000..08e7ee4bdf55
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/light/al3320a.yaml
>> @@ -0,0 +1,45 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only)
>
> Dual license new bindings:
>
> (GPL-2.0-only OR BSD-2-Clause)
It BSD usage in Linux kernel enforced for bindings?
Yes, bindings are exported and used by other projects. And may get
moved out completely.
So do I assume right if I'm not dual licencing also under BSD, patch
won't get merged?
By principle I don't like to being forced give my work to projects
which don't comply with GPL 2. Not much happy about it, but what can I
do, when I want this sensors DT merged in...
Due to the fact it's simple definition, I'll dual licence it also to
BSD for next patch version.
I'd like to publish my code only under GPL if possible.
