netdev - Re: [PATCH v5 net-next 3/5] amd-xgbe: add support for new XPCS routines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ecd1e9a6-4357-4a92-9024-a1b5c1f6496a@intel.com>
Date: Wed, 14 Feb 2024 14:14:01 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: Raju Rangoju <Raju.Rangoju@....com>, <netdev@...r.kernel.org>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
	<pabeni@...hat.com>, <Shyam-sundar.S-k@....com>, Sudheesh Mavila
	<sudheesh.mavila@....com>
Subject: Re: [PATCH v5 net-next 3/5] amd-xgbe: add support for new XPCS
 routines



On 2/14/2024 7:48 AM, Raju Rangoju wrote:
> +/*
> + * AMD 10Gb Ethernet driver
> + *
> + * This file is available to you under your choice of the following two
> + * licenses:
> + *
> + * License 1: GPLv2

<snip>

> + * License 2: Modified BSD
> + *

<snip>

> + *
> + *     Author: Raju Rangoju <Raju.Rangoju@....com>
> + */
I'm not sure if its a strict policy but I thought Linux kernel switched
to using SPDX headers instead of fully copying license information
within each file...

See: Documentation/process/license-rules.rst:

> An alternative to boilerplate text is the use of Software Package Data
> Exchange (SPDX) license identifiers in each source file.  SPDX license
> identifiers are machine parsable and precise shorthands for the license
> under which the content of the file is contributed.  SPDX license
> identifiers are managed by the SPDX Workgroup at the Linux Foundation and
> have been agreed on by partners throughout the industry, tool vendors, and
> legal teams.  For further information see https://spdx.org/
> 
> The Linux kernel requires the precise SPDX identifier in all source files.
> The valid identifiers used in the kernel are explained in the section
> `License identifiers`_ and have been retrieved from the official SPDX
> license list at https://spdx.org/licenses/ along with the license texts.

This implies to me that we should prefer SPDX license identifiers,
rather than including the boilerplate here.