1. 28 Feb, 2018 1 commit
  2. 25 Feb, 2018 1 commit
  3. 02 Nov, 2017 1 commit
    • Greg Kroah-Hartman's avatar
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman authored
      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 <5
         lines).
      
      All documentation files were explicitly excluded.
      
      The following heuristics were used to determine which SPDX license
      identifiers to apply.
      
       - when both scanners couldn't find any license traces, file was
         considered to have no license information in it, and the top level
         COPYING file license applied.
      
         For non */uapi/* files that summary was:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|-------
         GPL-2.0                                              11139
      
         and resulted in the first patch in this series.
      
         If that file was a */uapi/* path one, it was "GPL-2.0 WITH
         Linux-syscall-note" otherwise it was "GPL-2.0".  Results of that was:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|-------
         GPL-2.0 WITH Linux-syscall-note                        930
      
         and resulted in the second patch in this series.
      
       - if a file had some form of licensing information in it, and was one
         of the */uapi/* ones, it was denoted with the Linux-syscall-note if
         any GPL family license was found in the file or had no licensing in
         it (per prior point).  Results summary:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|------
         GPL-2.0 WITH Linux-syscall-note                       270
         GPL-2.0+ WITH Linux-syscall-note                      169
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17
         LGPL-2.1+ WITH Linux-syscall-note                      15
         GPL-1.0+ WITH Linux-syscall-note                       14
         ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5
         LGPL-2.0+ WITH Linux-syscall-note                       4
         LGPL-2.1 WITH Linux-syscall-note                        3
         ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3
         ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1
      
         and that resulted in the third patch in this series.
      
       - when the two scanners agreed on the detected license(s), that became
         the concluded license(s).
      
       - when there was disagreement between the two scanners (one detected a
         license but the other didn't, or they both detected different
         licenses) a manual inspection of the file occurred.
      
       - In most cases a manual inspection of the information in the file
         resulted in a clear resolution of the license that should apply (and
         which scanner probably needed to revisit its heuristics).
      
       - When it was not immediately clear, the license identifier was
         confirmed with lawyers working with the Linux Foundation.
      
       - If there was any question as to the appropriate license identifier,
         the file was flagged for further research and to be revisited later
         in time.
      
      In total, over 70 hours of logged manual review was done on the
      spreadsheet to determine the SPDX license identifiers to apply to the
      source files by Kate, Philippe, Thomas and, in some cases, confirmation
      by lawyers working with the Linux Foundation.
      
      Kate also obtained a third independent scan of the 4.13 code base from
      FOSSology, and compared selected files where the other two scanners
      disagreed against that SPDX file, to see if there was new insights.  The
      Windriver scanner is based on an older version of FOSSology in part, so
      they are related.
      
      Thomas did random spot checks in about 500 files from the spreadsheets
      for the uapi headers and agreed with SPDX license identifier in the
      files he inspected. For the non-uapi files Thomas did random spot checks
      in about 15000 files.
      
      In initial set of patches against 4.14-rc6, 3 files were found to have
      copy/paste license identifier errors, and have been fixed to reflect the
      correct identifier.
      
      Additionally Philippe spent 10 hours this week doing a detailed manual
      inspection and review of the 12,461 patched files from the initial patch
      version early this week with:
       - a full scancode scan run, collecting the matched texts, detected
         license ids and scores
       - reviewing anything where there was a license detected (about 500+
         files) to ensure that the applied SPDX license was correct
       - reviewing anything where there was no detection but the patch license
         was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
         SPDX license was correct
      
      This produced a worksheet with 20 files needing minor correction.  This
      worksheet was then exported into 3 different .csv files for the
      different types of files to be modified.
      
      These .csv files were then reviewed by Greg.  Thomas wrote a script to
      parse the csv files and add the proper SPDX tag to the file, in the
      format that the file expected.  This script was further refined by Greg
      based on the output to detect more types of files automatically and to
      distinguish between header and source .c files (which need different
      comment types.)  Finally Greg ran the script using the .csv files to
      generate the patches.
      Reviewed-by: default avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: default avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
  4. 25 Sep, 2017 1 commit
  5. 18 Aug, 2017 4 commits
  6. 11 Jun, 2017 1 commit
  7. 07 May, 2017 1 commit
  8. 27 Apr, 2017 2 commits
  9. 26 Apr, 2017 1 commit
  10. 14 Apr, 2017 1 commit
  11. 01 Apr, 2017 1 commit
    • simran singhal's avatar
      iio: proximity: as3935: constify attribute_group structures · 7ab89e1e
      simran singhal authored
      Check for attribute_group structures that are only stored in the
      attrs filed of iio_info structure. As the attrs field of iio_info
      structures is constant, so these attribute_group structures can also be
      declared constant.
      Done using coccinelle:
      
      @r1 disable optional_qualifier @
      identifier i;
      position p;
      @@
      static struct attribute_group i@p = {...};
      
      @ok1@
      identifier r1.i;
      position p;
      struct iio_info x;
      @@
      x.attrs=&i@p;
      
      @bad@
      position p!={r1.p,ok1.p};
      identifier r1.i;
      @@
      i@p
      
      @depends on !bad disable optional_qualifier@
      identifier r1.i;
      @@
      static
      +const
      struct attribute_group i={...};
      
      @depends on !bad disable optional_qualifier@
      identifier r1.i;
      @@
      +const
      struct attribute_group i;
      
      File size before:
         text	   data	    bss	    dec	    hex	filename
         4037	    288	      0	   4325	   10e5	drivers/iio/proximity/as3935.o
      
      File size after:
         text	   data	    bss	    dec	    hex	filename
         4101	    256	      0	   4357	   1105	drivers/iio/proximity/as3935.o
      Signed-off-by: default avatarsimran singhal <singhalsimran0@gmail.com>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
      7ab89e1e
  12. 19 Feb, 2017 1 commit
  13. 04 Feb, 2017 1 commit
    • Andreas Klinger's avatar
      iio: distance: add devantech us ranger srf04 · feda2840
      Andreas Klinger authored
      This patch adds support for the ultrasonic ranger srf04 of devantech.
      
      This device is measuring the distance of objects in a range between 1 cm
      and 3 meters and a theoretical resolution of 3 mm.
      
      There are two GPIOs used:
        - trigger: set as output to the device when the measurement should start
        - echo: set by the device when the ultrasonic wave is sent out and reset
          when the echo is recognized; this needs to be an interrupt input
      
      The time between setting and resetting the echo pin is the time the
      waveform needed for one round trip. This time is recorded in the interrupt
      handler.
      
      The distance is calculated in the read function by using the ultrasonic
      speed at 20 degrees celsius which is about 343 m/s.
      Signed-off-by: default avatarAndreas Klinger <ak@it-klinger.de>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
      feda2840
  14. 28 Jan, 2017 1 commit
    • Andreas Klinger's avatar
      iio: distance: srf08: add IIO driver for us ranger · 78f83902
      Andreas Klinger authored
      This is the IIO driver for devantech srf08 ultrasonic ranger which can be
      used to measure the distances to an object.
      
      The sensor supports I2C with some registers.
      
      Supported Features include:
       - read the distance in ranging mode in centimeters
       - output of the driver is directly the read value
       - together with the scale the driver delivers the distance in meters
       - only the first echo of the nearest object is delivered
       - set sensitivity as analog value in the range of 0-31  means setting
         gain register on device
       - set range registers; userspace enters max. range in millimeters in
         43 mm steps
      
      Features not supported by this driver:
       - ranging mode in inches or in microseconds
       - ANN mode
       - change I2C address through this driver
       - light sensor
      
      The driver was added in the directory "proximity" of the iio subsystem and
      the menu in den config is now called "Proximity and distance sensors"
      Signed-off-by: default avatarAndreas Klinger <ak@it-klinger.de>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
      78f83902
  15. 21 Jan, 2017 1 commit
  16. 31 Dec, 2016 1 commit
  17. 23 Oct, 2016 1 commit
  18. 03 Sep, 2016 1 commit
  19. 15 Aug, 2016 2 commits
  20. 30 Jun, 2016 1 commit
  21. 27 Jun, 2016 2 commits
  22. 11 Jun, 2016 1 commit
  23. 29 May, 2016 1 commit
  24. 22 May, 2016 3 commits
  25. 27 Feb, 2016 1 commit
  26. 03 Jan, 2016 1 commit
  27. 05 Dec, 2015 1 commit
  28. 22 Nov, 2015 1 commit
  29. 21 Nov, 2015 1 commit
    • Matt Ranostay's avatar
      iio: lidar: return -EINVAL on invalid signal · 45a6b821
      Matt Ranostay authored
      Returning zero from the measurment function has the side effect of
      corrupting the triggered buffer readings, better to use -EINVAL than
      a zero measurement reading.
      
      The INVALID status happens even it isn't out of range
      sometimes roughly once every second or two. This can be from an
      invalid second signal return path. Hence there are spurious zero
      readings from the triggered buffer, and warning messages in the kernel
      log.
      Signed-off-by: default avatarMatt Ranostay <mranostay@gmail.com>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
      45a6b821
  30. 28 Oct, 2015 1 commit
  31. 03 Oct, 2015 1 commit
  32. 30 Sep, 2015 1 commit