02 Nov, 2017

1 commit

  • Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

13 May, 2016

1 commit

  • ... making upstream development binutils snapshots work as expected,
    e.g.:

    $ mips64el-linux-ld --version
    GNU ld (GNU Binutils) 2.20.1.20100303
    [...]
    $

    Signed-off-by: Maciej W. Rozycki
    Acked-by: Michal Marek
    Cc: Michael S. Tsirkin
    Cc: James Hogan
    Cc: linux-kbuild@vger.kernel.org
    Cc: linux-mips@linux-mips.org
    Cc: linux-kernel@vger.kernel.org
    Patchwork: https://patchwork.linux-mips.org/patch/12537/
    Signed-off-by: Ralf Baechle

    Maciej W. Rozycki
     

13 Mar, 2016

1 commit

  • The ld-version.sh script fails on some versions of awk with the
    following error, resulting in build failures for MIPS:

    awk: scripts/ld-version.sh: line 4: regular expression compile failed (missing '(')

    This is due to the regular expression ".*)", meant to strip off the
    beginning of the ld version string up to the close bracket, however
    brackets have a meaning in regular expressions, so lets escape it so
    that awk doesn't expect a corresponding open bracket.

    Fixes: ccbef1674a15 ("Kbuild, lto: add ld-version and ld-ifversion ...")
    Reported-by: Geert Uytterhoeven
    Signed-off-by: James Hogan
    Tested-by: Michael S. Tsirkin
    Acked-by: Michael S. Tsirkin
    Tested-by: Sudip Mukherjee
    Cc: Michal Marek
    Cc: Andi Kleen
    Cc: Geert Uytterhoeven
    Cc: linux-mips@linux-mips.org
    Cc: linux-kbuild@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Cc: stable@vger.kernel.org # 4.4.x-
    Patchwork: https://patchwork.linux-mips.org/patch/12838/
    Signed-off-by: Ralf Baechle

    James Hogan
     

08 Jan, 2016

1 commit

  • On Fedora 23, ld --version outputs:
    GNU ld version 2.25-15.fc23

    But ld-version.sh fails to parse this, so e.g. mips build fails to
    enable VDSO, printing a warning that binutils >= 2.24 is required.

    To fix, teach ld-version to parse this format.

    Signed-off-by: Michael S. Tsirkin
    Cc: linux-kernel@vger.kernel.org
    Cc: Michal Marek
    Cc: linux-kbuild@vger.kernel.org
    Cc: linux-mips@linux-mips.org
    Patchwork: https://patchwork.linux-mips.org/patch/12023/
    Signed-off-by: Ralf Baechle

    Michael S. Tsirkin
     

04 Jan, 2016

1 commit

  • The ld-version.sh script doesn't handle versions with large (>= 10) 3rd
    version components, because the 2nd component is only multiplied by 10
    times that of the 3rd component.

    For example the following version string:
    GNU ld (Codescape GNU Tools 2015.06-05 for MIPS MTI Linux) 2.24.90

    gives a bogus version number:
    20000000
    + 2400000
    + 900000 = 23300000

    Breakage, confusion and mole-whacking ensues.

    Increase the multipliers of the first two version components by a factor
    of 10 to give space for a 3rd components of up to 99, and update the
    sole user of ld-ifversion (MIPS VDSO) accordingly.

    Signed-off-by: James Hogan
    Acked-by: Guenter Roeck
    Reviewed-by: Andi Kleen
    Cc: Andi Kleen
    Cc: Michal Marek
    Cc: Guenter Roeck
    Cc: linux-mips@linux-mips.org
    Cc: linux-kernel@vger.kernel.org
    Patchwork: https://patchwork.linux-mips.org/patch/11931/
    Signed-off-by: Ralf Baechle

    James Hogan
     

14 Feb, 2014

1 commit