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
     

07 Jan, 2011

1 commit

  • on building an uImage, I get:

    $ make uImage
    CHK include/linux/version.h
    CHK include/generated/utsrelease.h
    make[1]: `include/generated/mach-types.h' is up to date.
    CALL scripts/checksyscalls.sh
    CHK include/generated/compile.h
    Kernel: arch/arm/boot/Image is ready
    SHIPPED arch/arm/boot/compressed/lib1funcs.S
    AS arch/arm/boot/compressed/lib1funcs.o
    LD arch/arm/boot/compressed/vmlinux
    OBJCOPY arch/arm/boot/zImage
    Kernel: arch/arm/boot/zImage is ready
    UIMAGE arch/arm/boot/uImage
    "mkimage" command not found - U-Boot images will not be built
    Image arch/arm/boot/uImage is ready
    $

    I.e. it says: "uImage is ready" even though the uImage file doesn't
    exist because mkimage is missing.

    I propose the attached patch.

    Signed-off-by: Roland Stigge
    Signed-off-by: Michal Marek

    Roland Stigge
     

03 May, 2007

1 commit

  • I'm currently using CROSS_COMPILE="ccache arm-linux-". With that the bash
    builtin command "type" searches for ccache and arm-linux-mkimage and so sets
    MKIMAGE="/path/to/ccache" as I don't have arm-linux-mkimage. Then the script
    dies with an error, that ccache doesn't support the argument -A.

    This patch adds some quoting such that it works again for me.

    Please note that this patch doesn't help you if you use ${CROSSCOMPILE}-mkimage
    and ccache as mkuboot.sh now searches for the command
    "ccache arm-linux-mkimage".

    Signed-off-by: Uwe Kleine-König
    Signed-off-by: Sam Ravnborg

    Uwe kleine-König
     

15 Feb, 2007

1 commit

  • Check to see if `${CROSS_COMPILE}mkimage` exists and if not, fall back to
    the standard `mkimage`

    The Blackfin toolchain includes mkimage, but we dont want to namespace
    collide with any of the user's system setup, so we prefix it with our
    toolchain name.

    Signed-off-by: Mike Frysinger
    Cc: Sam Ravnborg
    Cc: Oleg Verych
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mike Frysinger
     

17 Apr, 2005

1 commit

  • 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