From: Arnd Bergmann <arnd@arndb.de>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"Kwok, WingMan" <w-kwok2@ti.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"ssantosh@kernel.org" <ssantosh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
KISHON VIJAY ABRAHAM <kishon@ti.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Quadros, Roger" <rogerq@ti.com>
Subject: Re: [PATCH v1 1/2] phy: keystone: serdes driver for gbe 10gbe and pcie
Date: Tue, 20 Oct 2015 10:24:18 +0200 [thread overview]
Message-ID: <4661946.mPHVFLWuan@wuerfel> (raw)
In-Reply-To: <56253B91.5040807@ti.com>
On Monday 19 October 2015 14:50:57 Murali Karicheri wrote:
> Arnd, by your statement 'I don't see any code that does this' do you
> expect a piece of code that embed the license in the binary image? If
> so, that seems weired to me.
>
> Many of the drivers including this patch has the following statement in
> the license that is additional company specific license such as BSD that
> is applicable.
>
> ==== Cut and pasted from drivers/crypto/fcrypt.c =======================
> * 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.
> =========================================================================
> I read this as if the source is compiled and distributed as a binary
> either a kernel module ko file or as part of the kernel binary, this
> term must apply. Usually this is part of documentation that goes with
> the product AFAIK.
Sorry, my fault. This is indeed the standard BSD license, and
I misread this as having to produce the copyright statement
from the binary itself. Please ignore whatever I said on the
subject.
Arnd
next prev parent reply other threads:[~2015-10-20 8:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 14:25 [PATCH v1 0/2] Common SerDes driver for TI's Keystone Platforms WingMan Kwok
2015-10-15 14:25 ` [PATCH v1 1/2] phy: keystone: serdes driver for gbe 10gbe and pcie WingMan Kwok
2015-10-15 14:51 ` Arnd Bergmann
2015-10-15 16:01 ` Murali Karicheri
2015-10-15 19:34 ` Arnd Bergmann
2015-10-19 14:47 ` Kwok, WingMan
2015-10-19 18:50 ` Murali Karicheri
2015-10-20 8:24 ` Arnd Bergmann [this message]
2015-10-20 15:11 ` Murali Karicheri
2015-10-15 20:08 ` Kwok, WingMan
2015-10-15 20:53 ` Arnd Bergmann
2015-10-15 23:57 ` Kwok, WingMan
2015-10-15 16:14 ` Rob Herring
2015-10-15 23:53 ` Kwok, WingMan
2015-10-15 14:25 ` [PATCH v1 2/2] PCI: keystone: update to use generic keystone serdes driver WingMan Kwok
[not found] ` <1444919145-30845-1-git-send-email-w-kwok2-l0cyMroinI0@public.gmane.org>
2015-10-15 16:51 ` [PATCH v1 0/2] Common SerDes driver for TI's Keystone Platforms Russell King - ARM Linux
2015-10-15 19:21 ` Kishon Vijay Abraham I
2015-10-16 0:02 ` Kwok, WingMan
[not found] ` <20151015165105.GE32532-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2015-10-16 1:00 ` Rob Herring
2015-10-16 8:02 ` Russell King - ARM Linux
2015-10-16 14:10 ` Murali Karicheri
2015-10-16 14:14 ` Kishon Vijay Abraham I
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=4661946.mPHVFLWuan@wuerfel \
--to=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m-karicheri2@ti.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=ssantosh@kernel.org \
--cc=w-kwok2@ti.com \
/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).