netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	linux-firmware@kernel.org, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README: clarify redistribution requirements covering patents
Date: Mon, 30 Jun 2014 19:53:51 +0200	[thread overview]
Message-ID: <20140630175351.GL27687@wotan.suse.de> (raw)
In-Reply-To: <20140628163108.0b8b81ce@alan.etchedpixels.co.uk>

On Sat, Jun 28, 2014 at 04:31:08PM +0100, One Thousand Gnomes wrote:
> > +the firmware license provided includes an implicit or explicit
> > +patent grant to end users to ensure full functionality of device
> > +operation with the firmware. If the licence is long and involved, it's
> >  permitted to include it in a separate file and refer to it from the
> >  WHENCE file.
> >  And if it were possible, a changelog of the firmware itself.
> 
> "end users of the device" or just "end users"
> 
> I'm assuming the worry for most vendors is licensing it to be used on
> some third party product ?

The proposed language includes both whereas the "end users of the device"
would exclude some subset use including the implicit license use case.
Thoughts?

  Luis

      reply	other threads:[~2014-06-30 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 19:39 [PATCH] README: clarify redistribution requirements covering patents Luis R. Rodriguez
2014-06-28 15:31 ` One Thousand Gnomes
2014-06-30 17:53   ` Luis R. Rodriguez [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=20140630175351.GL27687@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-firmware@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --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).