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
     

22 Sep, 2007

1 commit

  • Commit 69331af, "Fixes and cleanups for earlyprintk aka boot console",
    resulted in printk output prior to the initialization of the mpsc
    console driver not being printed. That commit causes the mpsc's
    CON_PRINTBUFFER flag to be cleared since udbg should have printed
    the previous output.

    I guess we can no longer ignore udbg. :)

    This patch provides udbg_putc() and udbg_getc() functions for the
    Marvell mv64x60 chips. These functions are enabled if an mv64x60
    port is to be used as the console as determined from the device tree.

    Signed-off-by: Dale Farnsworth
    Acked-by: Mark A. Greer
    Signed-off-by: Paul Mackerras

    Dale Farnsworth
     

12 May, 2007

2 commits

  • This patch adds PCI bridge support for the Marvell mv64x60 chip.
    We also provide the ability to read/write the mv64x60 hotswap
    register via sysfs if the hs_reg_valid property is set in the
    device tree.

    Signed-off-by: Dale Farnsworth
    Acked-by: Arnd Bergmann
    Signed-off-by: Paul Mackerras

    Dale Farnsworth
     
  • There are 3 interrupt groups each with its own status/mask registers.
    We use a separate struct irq_chip for each interrupt group and handle
    interrupts in two stages or levels: level 1 selects the appropriate
    struct irq_chip, and level 2 selects individual interrupts within
    that irq_chip.

    Signed-off-by: Dale Farnsworth
    Signed-off-by: Paul Mackerras

    Dale Farnsworth