From: Kyle McMartin <kyle@infradead.org>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Arend van Spriel <arend@broadcom.com>,
Kyle McMartin <kyle@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH resend] README: clarify redistribution requirements covering patents
Date: Tue, 19 May 2015 17:22:25 -0400 [thread overview]
Message-ID: <20150519212225.GD5093@merlin.infradead.org> (raw)
In-Reply-To: <CAB=NE6WxMid+eNOoHZ__kbvP3BktHuYip+fQwVDydJQbQ1No_g@mail.gmail.com>
On Tue, May 19, 2015 at 01:18:14PM -0700, Luis R. Rodriguez wrote:
> >> Your commit should include an update to the WHENCE file clearly
> >> identifying the licence under which the firmware is available, and
> >> -that it is redistributable. If the licence is long and involved, it's
> >> +that it is redistributable. Being redistributable includes ensuring
> >> +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
> >
> >
> > Just nitpicking here, but there is 'license' and 'licence' being used here.
> > Better stick to one and preferably 'license'.
>
> Fixed, will submit a v2.
>
Heh, it doesn't help that we now have LICENSE.* and LICENCE.* in the
tree as well. :/ I believe, at least in my Commonwealth english, that
licence is the file, and license is the action of licensing. I should
probably rename the LICENSE.* files in the tree to match.
--Kyle
prev parent reply other threads:[~2015-05-19 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 17:56 [PATCH resend] README: clarify redistribution requirements covering patents Luis R. Rodriguez
2015-05-14 18:29 ` Arend van Spriel
[not found] ` <5554E99A.5030302-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-05-19 20:18 ` Luis R. Rodriguez
2015-05-19 21:22 ` Kyle McMartin [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=20150519212225.GD5093@merlin.infradead.org \
--to=kyle@infradead.org \
--cc=arend@broadcom.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=kyle@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).