devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Rob Herring <robh@kernel.org>
Cc: "Dmitry Osipenko" <digetx@gmail.com>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Daniel Baluta" <daniel.baluta@nxp.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Hartmut Knaack" <knaack.h@gmx.de>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
	"Mark Rutland" <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH v4 1/7] dt-bindings: iio: light: add support for Dyna-Image AL3320A
Date: Thu, 06 Feb 2020 22:44:37 +0100	[thread overview]
Message-ID: <1581025477.790008.1@ixit.cz> (raw)
In-Reply-To: <CAL_JsqKQm7rnfm=QZSS+83czgaLoE6Wtg2se9r0ayvMgtfd-ZQ@mail.gmail.com>




Rob Herring <robh@kernel.org> napsal Čt, 6. úno 2020 v 14∶27:
> On Thu, Feb 6, 2020 at 2:16 PM David Heidelberg <david@ixit.cz> wrote:
>> 
>> 
>> 
>> 
>>  Rob Herring <robh@kernel.org> 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@ixit.cz>
>>  >>  ---
>>  >>   .../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.



  reply	other threads:[~2020-02-06 21:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200204093031.616409-1-david@ixit.cz>
2020-02-04  9:30 ` [PATCH v4 1/7] dt-bindings: iio: light: add support for Dyna-Image AL3320A David Heidelberg
2020-02-06 19:07   ` Rob Herring
2020-02-06 21:16     ` David Heidelberg
2020-02-06 21:27       ` Rob Herring
2020-02-06 21:44         ` David Heidelberg [this message]
2020-02-04  9:30 ` [PATCH v4 2/7] dt-bindings: iio: light: add support for Dyna-Image AL3010 David Heidelberg
2020-02-04  9:52   ` Michał Mirosław
2020-02-04 15:10     ` Dmitry Osipenko

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=1581025477.790008.1@ixit.cz \
    --to=david@ixit.cz \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=pmeerw@pmeerw.net \
    --cc=robh@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).