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: <20160918020414.GP10601@decadent.org.uk>
Date:   Sun, 18 Sep 2016 03:04:14 +0100
From:   Ben Hutchings <ben@...adent.org.uk>
To:     linux-kernel@...r.kernel.org, linux-firmware@...nel.org
Subject: [PATCH linux-firmware 12/12] README: Say that files must be listed
 in WHENCE, and how to check it

- Say that new files must, not 'should', be listed in WHENCE
- State the expected form of a reference to a separate licence file
- Mention 'make check'

Signed-off-by: Ben Hutchings <ben@...adent.org.uk>
---
 README | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/README b/README
index cdaecf04b46e..77ff0106c483 100644
--- a/README
+++ b/README
@@ -16,16 +16,19 @@ diff or preferably a git pull request to:
       linux-firmware@...nel.org
 and also cc: to related mailing lists.
 
-Your commit should include an update to the WHENCE file clearly
-identifying the license under which the firmware is available, and
+If your commit adds new firmware, it must update the WHENCE file to
+clearly state the license under which the firmware is available, and
 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 license is long and involved, it's
 permitted to include it in a separate file and refer to it from the
-WHENCE file.
+WHENCE file ('See LICENSE.foo for details.').
 And if it were possible, a changelog of the firmware itself.
 
+Run 'make check' to check that WHENCE is consistent with the
+repository contents.
+
 Ideally, your commit should contain a Signed-Off-By: from someone
 authoritative on the licensing of the firmware in question (i.e. from
 within the company that owns the code).

Download attachment "signature.asc" of type "application/pgp-signature" (812 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ