linux-kernel - [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy

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-next>] [day] [month] [year] [list]

Message-ID: <20171016092515.GA29207@kroah.com>
Date:   Mon, 16 Oct 2017 11:25:15 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: [GIT PULL] Documentation: Add a file explaining the requested Linux
 kernel license enforcement policy

The following changes since commit 33d930e59a98fa10a0db9f56c7fa2f21a4aef9b9:

  Linux 4.14-rc5 (2017-10-15 21:01:12 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/enforcement-4.14-rc6

for you to fetch changes up to 9ed95129ffcabbde564b40ffbbf9c26e8702d858:

  Documentation: Add a file explaining the Linux kernel license enforcement policy (2017-10-16 11:14:43 +0200)

----------------------------------------------------------------
Documentation: Add a file explaining the requested Linux kernel license enforcement policy

Here's a pull request to add a new file to the kernel's Documentation directory.
It adds a short document describing the views of how the Linux kernel community
feels about enforcing the license of the kernel.

The patch has been reviewed by a large number of kernel developers already, as
seen by their acks on the patch, and their agreement of the statement with
their names on it.  The location of the file was also agreed upon by the
Documentation maintainer, so all should be good there.

For some background information about this statement, see this article
written by some of the kernel developers involved in drafting it:
	http://kroah.com/log/blog/2017/10/16/linux-kernel-community-enforcement-statement/
and this article that answers a number of questions that came up in the
discussion of this statement with the kernel developer community:
	http://kroah.com/log/blog/2017/10/16/linux-kernel-community-enforcement-statement-faq/

If anyone has any further questions about it, please let me, and the TAB
members, know and we will be glad to help answer them.

Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

----------------------------------------------------------------
Greg Kroah-Hartman (1):
      Documentation: Add a file explaining the Linux kernel license enforcement policy

 Documentation/process/index.rst                    |   1 +
 .../process/kernel-enforcement-statement.rst       | 147 +++++++++++++++++++++
 2 files changed, 148 insertions(+)
 create mode 100644 Documentation/process/kernel-enforcement-statement.rst