Eric Lee / smarc-fsl-linux-kernel

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
     

27 Jul, 2010

2 commits

  • b5e477290   firewire: nosy: misc cleanups ... Browse Code »

    Extend copyright note to 2007, c.f. Kristian's git log.

    Includes:
    - replace some by
    - add required indirectly included
    - order alphabetically

    Coding style related changes:
    - change to utf8
    - normalize whitespace
    - normalize comment style
    - remove usages of __FUNCTION__
    - remove an unnecessary cast from void *

    Const and static declarations:
    - driver_name is not const in pci_driver.name, drop const qualifier
    - driver_name can be taken from KBUILD_MODNAME
    - the global variable minors[] can and should be static
    - constify struct file_operations instance

    Data types:
    - Remove unused struct member struct packet.code. struct packet is
    only used for driver-internal bookkeeping; it does not appear on the
    wire or in DMA programs or the userspace ABI. Hence the unused
    member .code can be removed without worries.

    Preprocessor macros:
    - unroll a preprocessor macro that containd a return
    - use list_for_each_entry

    Printk:
    - add missing terminating \n in some format strings

    Signed-off-by: Stefan Richter

    Stefan Richter
     
  • 286468210   firewire: new driver: nosy - IEEE 1394 traffic sniffer ... Browse Code »

    This adds the traffic sniffer driver for Texas Instruments PCILynx/
    PCILynx2 based cards. The use cases for nosy are analysis of
    nonstandard protocols and as an aid in development of drivers,
    applications, or firmwares.

    Author of the driver is Kristian Høgsberg. Known contributers are
    Jody McIntyre and Jonathan Woithe.

    Nosy programs PCILynx chips to operate in promiscuous mode, which is a
    feature that is not found in OHCI-1394 controllers. Hence, only special
    hardware as mentioned in the Kconfig help text is suitable for nosy.

    This is only the kernelspace part of nosy. There is a userspace
    interface to it, called nosy-dump, proposed to be added into the tools/
    subdirectory of the kernel sources in a subsequent change. Kernelspace
    and userspave component of nosy communicate via a 'misc' character
    device file called /dev/nosy with a simple ioctl() and read() based
    protocol, as described by nosy-user.h.

    The files added here are taken from
    git://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)
    with the following changes by Stefan Richter:
    - Kconfig and Makefile hunks are written from scratch.
    - Commented out version printk in nosy.c.
    - Included missing , reported by Stephen Rothwell.

    "git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:

    Jonathan Woithe (2):
    Nosy updates for recent kernels
    Fix uninitialised memory (needed for 2.6.31 kernel)

    Kristian Høgsberg (5):
    Pull over nosy from mercurial repo.
    Use a misc device instead.
    Add simple AV/C decoder.
    Don't break down on big payloads.
    Set parent device for misc device.

    As a low-level IEEE 1394 driver, its files are placed into
    drivers/firewire/ although nosy is not part of the firewire driver
    stack.

    I am aware of the following literature from Texas Instruments about
    PCILynx programming:
    SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF
    Functional Specification
    SLLA023 - Initialization and Asynchronous Programming of the
    TSB12LV21A 1394 Device

    Signed-off-by: Stefan Richter
    Acked-by: Kristian Høgsberg

    Stefan Richter