netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Manlunas, Felix" <Felix.Manlunas@cavium.com>
Cc: "linux-firmware@kernel.org" <linux-firmware@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"fweimer@redhat.com" <fweimer@redhat.com>,
	"Awasthi, Manish" <Manish.Awasthi@cavium.com>,
	"Panicker, Manojkumar" <Manojkumar.Panicker@cavium.com>,
	"Masood, Faisal" <Faisal.Masood@cavium.com>,
	"Vatsavayi, Raghu" <Raghu.Vatsavayi@cavium.com>,
	"Chickles, Derek" <Derek.Chickles@cavium.com>,
	"Burla, Satananda" <Satananda.Burla@cavium.com>
Subject: Re: [PATCH linux-firmware] linux-firmware: liquidio: fix GPL compliance issue
Date: Wed, 17 Oct 2018 16:11:50 -0400	[thread overview]
Message-ID: <20181017201149.GC1381@tuxdriver.com> (raw)
In-Reply-To: <20181017193438.GA4435@felix-thinkpad.cavium.com>

On Wed, Oct 17, 2018 at 07:34:42PM +0000, Manlunas, Felix wrote:
> On Fri, Sep 28, 2018 at 04:50:51PM -0700, Felix Manlunas wrote:
> > Part of the code inside the lio_vsw_23xx.bin firmware image is under GPL,
> > but the LICENCE.cavium file neglects to indicate that.  However,
> > LICENCE.cavium does correctly specify the license that covers the other
> > Cavium firmware images that do not contain any GPL code.
> > 
> > Fix the GPL compliance issue by adding a new file, LICENCE.cavium_liquidio,
> > which correctly shows the GPL boilerplate.  This new file specifies the
> > licenses for all liquidio firmware, including the ones that do not have
> > GPL code.
> > 
> > Change the liquidio section of WHENCE to point to LICENCE.cavium_liquidio.
> > 
> > Reported-by: Florian Weimer <fweimer@redhat.com>
> > Signed-off-by: Manish Awasthi <manish.awasthi@cavium.com>
> > Signed-off-by: Manoj Panicker <manojkumar.panicker@cavium.com>
> > Signed-off-by: Faisal Masood <faisal.masood@cavium.com>
> > Signed-off-by: Felix Manlunas <felix.manlunas@cavium.com>
> > ---
> >  LICENCE.cavium_liquidio | 429 ++++++++++++++++++++++++++++++++++++++++++++++++
> >  WHENCE                  |   2 +-
> >  2 files changed, 430 insertions(+), 1 deletion(-)
> >  create mode 100644 LICENCE.cavium_liquidio
> 
> Hello Maintainers of linux-firmware.git,
> 
> Any feedback about this patch?

I would prefer to see an offer that included a defined URL for anyone
to download the source for the kernel in question without having to
announce themselves. The "send an email to info@cavium.com" offer may
(or may not) be sufficient for the letter of the law. But it seems
both fragile and prone to subjective frustrations and delays for
users to obtain the sources at some future date.

Respectfully,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2018-10-18  4:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 23:50 [PATCH linux-firmware] linux-firmware: liquidio: fix GPL compliance issue Manlunas, Felix
2018-10-17 19:34 ` Manlunas, Felix
2018-10-17 20:11   ` John W. Linville [this message]
2018-10-18 19:04     ` Josh Boyer

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=20181017201149.GC1381@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Derek.Chickles@cavium.com \
    --cc=Faisal.Masood@cavium.com \
    --cc=Felix.Manlunas@cavium.com \
    --cc=Manish.Awasthi@cavium.com \
    --cc=Manojkumar.Panicker@cavium.com \
    --cc=Raghu.Vatsavayi@cavium.com \
    --cc=Satananda.Burla@cavium.com \
    --cc=fweimer@redhat.com \
    --cc=linux-firmware@kernel.org \
    --cc=netdev@vger.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).