From: Arend van Spriel <arend@broadcom.com>
To: Jarl Friis <jarl@softace.dk>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Stefano Brivio" <stefano.brivio@polimi.it>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
b43-dev@lists.infradead.org
Subject: [PATCH 2/2] Using LP firmware for taking advantage of the low-power capabilities.
Date: Wed, 19 Sep 2012 21:33:02 +0200 [thread overview]
Message-ID: <505A1DEE.9010905@broadcom.com> (raw)
In-Reply-To: <CAOjsGA25PR9OCC_cAVn=gztk9YB6pNxCz=1mFjDxxQoc-tofEw@mail.gmail.com>
On 09/19/2012 08:54 PM, Jarl Friis wrote:
>> Is the addition of your copyright to the driver
>> >warranted by this change?
> As far as I understand the copyright law: Yes, but I'm not an expert.
> Neither am I 100% sure what you mean.
You add your name to the copy notice of the file so you claim it for the
entire file.
>> >For example, I have made much larger contributions
>> >to b43 over the years before I started doing reverse-engineering on this
>> >driver, but I never added my copyright.
> I suggest you do.
Typically, the names you see there are and/or were b43 maintainers.
>> >Your "Signed-off-by" implies
>> >copyright for the patch.
> The fact that I authored the patch implies copyright (even without
> Signed-off-by)
>
> Jarl
You can indeed claim it for your patch, but I think not beyond that. But
I am no lawyer either so .....pffff.
Gr. AvS
next prev parent reply other threads:[~2012-09-19 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 11:18 [PATCH 1/2] Added information about which firmware file is being requested Jarl Friis
2012-09-19 11:18 ` [PATCH 2/2] Using LP firmware for taking advantage of the low-power capabilities Jarl Friis
2012-09-19 15:08 ` Larry Finger
2012-09-19 18:54 ` Jarl Friis
2012-09-19 19:33 ` Arend van Spriel [this message]
2012-09-19 19:40 ` Jarl Friis
2012-09-19 20:10 ` Jarl Friis
2012-09-20 6:05 ` Rafał Miłecki
2012-09-20 6:32 ` Jarl Friis
2012-09-19 12:39 ` [PATCH 1/2] Added information about which firmware file is being requested Julian Calaby
2012-09-19 18:42 ` Michael Tokarev
2012-09-19 18:56 ` Jarl Friis
2012-09-20 6:06 ` Rafał Miłecki
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=505A1DEE.9010905@broadcom.com \
--to=arend@broadcom.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=jarl@softace.dk \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=stefano.brivio@polimi.it \
/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).