1. 04 Jul, 2018 1 commit
  2. 30 Apr, 2018 2 commits
  3. 29 Jan, 2018 3 commits
  4. 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
  5. 04 May, 2016 2 commits
  6. 23 Jun, 2015 1 commit
  7. 26 May, 2014 1 commit
  8. 03 Apr, 2014 1 commit
    • Liu Ying's avatar
      backlight: update bd state & fb_blank properties when necessary · a55944ca
      Liu Ying authored
      We don't have to update the state and fb_blank properties of a backlight
      device every time a blanking or unblanking event comes because they may
      have already been what we want.  Another thought is that one backlight
      device may be shared by multiple framebuffers.  The backlight driver
      should take the backlight device as a resource shared by all the
      associated framebuffers.
      
      This patch adds some logic to record each framebuffer's backlight usage
      to determine the backlight device use count and whether the two
      properties should be updated or not.  To be more specific, only one
      unblank operation on a certain blanked framebuffer may increase the
      backlight device's use count by one, while one blank operation on a
      certain unblanked framebuffer may decrease the use count by one, because
      the userspace is likely to unblank an unblanked framebuffer or blank a
      blanked framebuffer.
      Signed-off-by: default avatarLiu Ying <Ying.Liu@freescale.com>
      Cc: Jingoo Han <jg1.han@samsung.com>
      Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: Jani Nikula <jani.nikula@linux.intel.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      a55944ca
  9. 15 Oct, 2013 1 commit
  10. 03 Jul, 2013 1 commit
  11. 18 Dec, 2012 1 commit
  12. 23 Mar, 2011 1 commit
    • Matthew Garrett's avatar
      backlight: add backlight type · bb7ca747
      Matthew Garrett authored
      There may be multiple ways of controlling the backlight on a given
      machine.  Allow drivers to expose the type of interface they are
      providing, making it possible for userspace to make appropriate policy
      decisions.
      Signed-off-by: default avatarMatthew Garrett <mjg@redhat.com>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Chris Wilson <chris@chris-wilson.co.uk>
      Cc: David Airlie <airlied@linux.ie>
      Cc: Alex Deucher <alexdeucher@gmail.com>
      Cc: Ben Skeggs <bskeggs@redhat.com>
      Cc: Zhang Rui <rui.zhang@intel.com>
      Cc: Len Brown <lenb@kernel.org>
      Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      bb7ca747
  13. 16 Mar, 2010 3 commits
  14. 16 Dec, 2009 1 commit
  15. 21 Sep, 2009 1 commit
  16. 08 Jan, 2009 1 commit
  17. 11 Oct, 2007 1 commit
  18. 16 Jul, 2007 1 commit
  19. 20 Feb, 2007 4 commits
  20. 20 Dec, 2006 1 commit
    • Yu Luming's avatar
      ACPI: video: Add dev argument for backlight_device_register · 519ab5f2
      Yu Luming authored
      This patch set adds generic abstract layer support for acpi video driver to
      have generic user interface to control backlight and output switch control by
      leveraging the existing backlight sysfs class driver, and by adding a new
      video output sysfs class driver.
      
      This patch:
      
      Add dev argument for backlight_device_register to link the class device to
      real device object.  The platform specific driver should find a way to get the
      real device object for their video device.
      
      [akpm@osdl.org: build fix]
      [akpm@osdl.org: fix msi-laptop.c]
      Signed-off-by: default avatarLuming Yu <Luming.yu@intel.com>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      519ab5f2
  21. 31 Mar, 2006 1 commit
    • Richard Purdie's avatar
      [PATCH] backlight: Backlight Class Improvements · 6ca01765
      Richard Purdie authored
      Backlight class attributes are currently easy to implement incorrectly.
      Moving certain handling into the backlight core prevents this whilst at the
      same time makes the drivers simpler and consistent.  The following changes are
      included:
      
      The brightness attribute only sets and reads the brightness variable in the
      backlight_properties structure.
      
      The power attribute only sets and reads the power variable in the
      backlight_properties structure.
      
      Any framebuffer blanking events change a variable fb_blank in the
      backlight_properties structure.
      
      The backlight driver has only two functions to implement.  One function is
      called when any of the above properties change (to update the backlight
      brightness), the second is called to return the current backlight brightness
      value.  A new attribute "actual_brightness" is added to return this brightness
      as determined by the driver having combined all the above factors (and any
      driver/device specific factors).
      
      Additionally, the backlight core takes care of checking the maximum brightness
      is not exceeded and of turning off the backlight before device removal.
      
      The corgi backlight driver is updated to reflect these changes.
      Signed-off-by: default avatarRichard Purdie <rpurdie@rpsys.net>
      Signed-off-by: default avatarAntonino Daplas <adaplas@pol.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      6ca01765
  22. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!
      1da177e4