Eric Lee / smarc-fsl-linux-kernel

04 Mar, 2019

1 commit

02 Nov, 2017

1 commit

  • b24413180   License cleanup: add SPDX GPL-2.0 license identifier to files with no license ... Browse Code »

    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
     

20 Aug, 2014

1 commit

03 Oct, 2012

1 commit

  • b1e0d8b70   kbuild: Fix gcc -x syntax ... Browse Code »

    The correct syntax for gcc -x is "gcc -x assembler", not
    "gcc -xassembler". Even though the latter happens to work, the former
    is what is documented in the manual page and thus what gcc wrappers
    such as icecream do expect.

    This isn't a cosmetic change. The missing space prevents icecream from
    recognizing compilation tasks it can't handle, leading to silent kernel
    miscompilations.

    Besides me, credits go to Michael Matz and Dirk Mueller for
    investigating the miscompilation issue and tracking it down to this
    incorrect -x parameter syntax.

    Signed-off-by: Jean Delvare
    Acked-by: Ingo Molnar
    Cc: stable@vger.kernel.org
    Cc: Bernhard Walle
    Cc: Michal Marek
    Cc: Ralf Baechle
    Signed-off-by: Michal Marek

    Jean Delvare
     

10 Jun, 2009

1 commit

  • bdefe35d4   Remove bashisms from scripts ... Browse Code »

    The '-e' option to echo and brace expansion are not guaranteed to be supported
    by a POSIX-compliant /bin/sh (e.g. dash)

    Signed-off-by: dann frazier
    Signed-off-by: Andrew Morton
    Signed-off-by: Sam Ravnborg

    dann frazier
     

29 Jan, 2008

1 commit

  • 0484f1299   kbuild: fix buglet in gcc-version.sh ... Browse Code »

    Greg Schafer reported:
    ====
    $make mrproper
    scripts/gcc-version.sh: [[: command not found

    This is on a very old host with an ancient bash as /bin/sh. But I have
    CONFIG_SHELL set and pointing to a modern bash. Something is wrong.

    This doesn't happen with 2.6.23
    ====

    Fixed using a more common string equality test.

    Signed-off-by: Sam Ravnborg
    Cc: Greg Schafer
    Cc: Jesper Juhl

    Sam Ravnborg
     

13 Oct, 2007

1 commit

  • de47062a1   kbuild: improve scripts/gcc-version.sh output a bit when called without args ... Browse Code »

    Currently, if you call scripts/gcc-version.sh without arguments it will
    generate this output :

    $ sh scripts/gcc-version.sh
    scripts/gcc-version.sh: line 12: [: =: unary operator expected
    scripts/gcc-version.sh: line 16: -E: command not found
    scripts/gcc-version.sh: line 17: -E: command not found
    0000

    Not too pretty. I believe this is an improvement :

    $ sh scripts/gcc-version.sh
    Error: No compiler specified.
    Usage:
    scripts/gcc-version.sh

    Signed-off-by: Jesper Juhl
    Signed-off-by: Sam Ravnborg

    Jesper Juhl
     

17 Jul, 2007

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds