All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] nfs: convert supported_nfs_versions bitfield to an enum
Date: Tue, 30 Oct 2018 09:53:35 +0100	[thread overview]
Message-ID: <CAAh8qsxgdDwdP9125FZet4MbqN7a=Rf_rMDOrgDLhm82CqBXpw@mail.gmail.com> (raw)
In-Reply-To: <20181030084631.8688424004C@gemini.denx.de>

Wolfgang Denk <wd@denx.de> schrieb am Di., 30. Okt. 2018, 09:46:

> Dear Joe,
>
> In message <CANr=Z=a1+UFV+gU=3a5wPz7UpH-mzsvB-+FZd=
> LD8JTXR3gRGg at mail.gmail.com> you wrote:
> >
> > > As the maintainer of lwIP, I already have thought about this more than
> > > once. My main concern however was the license (lwIP is BSD style) and
> >
> > Yes, the license is a concern. I'm not a lawyer, but maybe someone can
> > comment on what our options are here. Wolfgang? Tom?
>
> IANAL...
>
> Fact is, we already have some 80+ source files in U-Boot which are
> covered by the BSD-3-Clause license.  Apparently there are also
> statements from the FSF that BSD-3-Clause is considered compatible
> with GPLv2.
>
> My _personal_ opinion is that I try to avoid BSD-3-Clause because of
> both the:
>
>         2. Redistributions in binary form must reproduce the above
>            copyright notice, this list of conditions and the
>            following disclaimer in the documentation and/or other
>            materials provided with the distribution.
>
> and the
>
>         3. The name of the author may not be used to endorse or
>            promote products derived from this software without
>            specific prior written permission.
>
> clauses.
>
> The former forces me to add "some text" to all documentation, and
> the latter forbids me to say who wrote the code as this might be
> considered promotion of the product.  Both are obligations I have
> to adhere to, while GPL clearly says "You may not impose any further
> restrictions on the recipients' exercise of the rights granted
> herein."  So in my opinion BSD-3-Clause should be avoided - but
> then, this is just my $0.02 - YMMV.
>
> I take chances to have lwIP relicenced under a dual license (GPLv2
> OR BSD-3-Clause) are epsilon?
>

Given that I am not the only author but lwIP has a long history of
contributors, I don't know how I should handle such a license change...

Simon

      reply	other threads:[~2018-10-30  8:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01  9:46 [U-Boot] [PATCH 1/4] nfs: convert supported_nfs_versions bitfield to an enum Christian Gmeiner
2018-10-01  9:46 ` [U-Boot] [PATCH 2/4] nfs: factor out generic reply error handling Christian Gmeiner
2018-10-01  9:46 ` [U-Boot] [PATCH 3/4] nfs: handle rpc errors for mount calls Christian Gmeiner
2018-10-01  9:46 ` [U-Boot] [PATCH 4/4] net: add NFSv1 support Christian Gmeiner
2018-10-01 13:08 ` [U-Boot] [PATCH 1/4] nfs: convert supported_nfs_versions bitfield to an enum Wolfgang Denk
2018-10-01 13:56   ` Christian Gmeiner
2018-10-22 18:53     ` Joe Hershberger
2018-10-22 19:39       ` Simon Goldschmidt
2018-10-29 20:05         ` Joe Hershberger
2018-10-29 22:13           ` Tom Rini
2018-10-30  8:46           ` Wolfgang Denk
2018-10-30  8:53             ` Simon Goldschmidt [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='CAAh8qsxgdDwdP9125FZet4MbqN7a=Rf_rMDOrgDLhm82CqBXpw@mail.gmail.com' \
    --to=simon.k.r.goldschmidt@gmail.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.