1. 30 Mar, 2018 1 commit
  2. 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
  3. 02 Oct, 2017 1 commit
  4. 09 Sep, 2017 1 commit
  5. 07 Aug, 2014 1 commit
  6. 17 Oct, 2012 1 commit
    • David Howells's avatar
      UAPI: Remove empty non-UAPI Kbuild files · 64d7155c
      David Howells authored
      Remove non-UAPI Kbuild files that have become empty as a result of UAPI
      disintegration.  They used to have only header-y lines in them and those have
      now moved to the Kbuild files in the corresponding uapi/ directories.
      
      Possibly these should not be removed but rather have a comment inserted to say
      they are intentionally left blank.  This would make it easier to add generated
      header lines in future without having to restore the infrastructure.
      
      Note that at this point not all the UAPI disintegration parts have been merged,
      so it is likely that more empty Kbuild files will turn up.
      
      It is probably necessary to make the files non-empty to prevent the patch
      program from automatically deleting them when it reduces them to nothing.
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      64d7155c
  7. 13 Oct, 2012 1 commit
  8. 14 Aug, 2010 1 commit
  9. 26 May, 2010 1 commit
    • Linus Torvalds's avatar
      Revert "endian: #define __BYTE_ORDER" · 13da9e20
      Linus Torvalds authored
      This reverts commit b3b77c8c, which was
      also totally broken (see commit 0d2daf5c that reverted the crc32
      version of it).  As reported by Stephen Rothwell, it causes problems on
      big-endian machines:
      
      > In file included from fs/jfs/jfs_types.h:33,
      >                  from fs/jfs/jfs_incore.h:26,
      >                  from fs/jfs/file.c:22:
      > fs/jfs/endian24.h:36:101: warning: "__LITTLE_ENDIAN" is not defined
      
      The kernel has never had that crazy "__BYTE_ORDER == __LITTLE_ENDIAN"
      model.  It's not how we do things, and it isn't how we _should_ do
      things.  So don't go there.
      Requested-by: default avatarStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      13da9e20
  10. 25 May, 2010 1 commit
  11. 07 Jan, 2009 1 commit
    • Harvey Harrison's avatar
      byteorder: only use linux/swab.h · 991c0e6d
      Harvey Harrison authored
      The first step to make swab.h a regular header that will
      include an asm/swab.h with arch overrides.
      
      Avoid the gratuitous differences introduced in the new
      linux/swab.h by naming the ___constant_swabXX bits and
      __fswabXX bits exactly as found in the old implementation
      in byteorder/swab[b].h
      
      Use this new swab.h in byteorder/[big|little]_endian.h and
      remove the two old swab headers.
      
      Although the inclusion of asm/byteorder.h looks strange in
      linux/swab.h, this will allow each arch to move the actual
      arch overrides for the swab bits in an asm file and then
      the includes can be cleaned up without requiring a flag day
      for all arches at once.
      
      Keep providing __fswabXX in case some userspace was using them
      directly, but the revised __swabXX should be used instead in
      any new code and will always do constant folding not dependent
      on the optimization level, which means the __constant versions
      can be phased out in-kernel.
      
      Arches that use the old-style arch macros will lose their
      optimized versions until they move to the new style, but at
      least they will still compile.  Many arches have already moved
      and the patches to move the remaining arches are trivial.
      Signed-off-by: Harvey Harrison's avatarHarvey Harrison <harvey.harrison@gmail.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      991c0e6d
  12. 20 Oct, 2008 1 commit
  13. 25 Jul, 2008 1 commit
  14. 30 Apr, 2008 1 commit
  15. 08 Feb, 2008 1 commit
    • Marcin Slusarz's avatar
      byteorder: move le32_add_cpu & friends from OCFS2 to core · 8b5f6883
      Marcin Slusarz authored
      This patchset moves le*_add_cpu and be*_add_cpu functions from OCFS2 to core
      header (1st), converts ext3 filesystem to this API (2nd) and replaces XFS
      different named functions with new ones (3rd).
      
      There are many places where these functions will be useful.  Just look at:
      grep -r 'cpu_to_[ble12346]*([ble12346]*_to_cpu.*[-+]' linux-src/ Patch for
      ext3 is an example how conversions will probably look like.
      
      This patch:
      
      - move inline functions which add native byte order variable to
        little/big endian variable to core header
        * le16_add_cpu(__le16 *var, u16 val)
        * le32_add_cpu(__le32 *var, u32 val)
        * le64_add_cpu(__le64 *var, u64 val)
        * be32_add_cpu(__be32 *var, u32 val)
      - add for completeness:
        * be16_add_cpu(__be16 *var, u16 val)
        * be64_add_cpu(__be64 *var, u64 val)
      Signed-off-by: default avatarMarcin Slusarz <marcin.slusarz@gmail.com>
      Acked-by: default avatarMark Fasheh <mark.fasheh@oracle.com>
      Cc: David Chinner <dgc@sgi.com>
      Cc: Timothy Shimmin <tes@sgi.com>
      Cc: <linux-ext4@vger.kernel.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      8b5f6883
  16. 08 May, 2007 2 commits
    • Michal Schmidt's avatar
      Fix compilation of drivers with -O0 · ee7b9e37
      Michal Schmidt authored
      It is sometimes useful to compile individual drivers with optimization
      disabled for easier debugging.  Currently drivers which use htonl() and
      similar functions don't compile with -O0.  This patch fixes it.  It also
      removes obsolete and misleading comments.  This header is not for
      userspace, so we don't have to care about strange programs these comments
      mention.
      
      (akpm: -O0 probably isn't a good idea, but this code looks pretty crufty and
      unuseful)
      Signed-off-by: default avatarMichal Schmidt <mschmidt@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      ee7b9e37
    • Trent Piepho's avatar
      Fix constant folding and poor optimization in byte swapping code · 8e2c2002
      Trent Piepho authored
      Constant folding does not work for the swabXX() byte swapping functions,
      and the C versions optimize poorly.
      
      Attempting to initialize a global variable to swab16(0x1234) or put
      something like "case swab32(42):" in a switch statement will not compile.
      It can work, swab.h just isn't doing it correctly.  This patch fixes that.
      
      Contrary to the comment in asm-i386/byteorder.h, gcc does not recognize the
      "C" version of swab16 and turn it into efficient code.  gcc can do this,
      just not with the current code.  The simple function:
      
      u16 foo(u16 x) { return swab16(x); }
      
      Would compile to:
              movzwl  %ax, %eax
              movl    %eax, %edx
              shrl    $8, %eax
              sall    $8, %edx
              orl     %eax, %edx
      
      With this patch, it will compile to:
              rolw    $8, %ax
      
      I also attempted to document the maze different macros/inline functions
      that are used to create the final product.
      Signed-off-by: default avatarTrent Piepho <xyzzy@speakeasy.org>
      Cc: Francois-Rene Rideau <fare@tunes.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      8e2c2002
  17. 11 Feb, 2007 2 commits
  18. 19 Sep, 2006 1 commit
  19. 18 Jun, 2006 1 commit
  20. 09 Jan, 2006 1 commit
  21. 20 Sep, 2005 1 commit
  22. 29 Jun, 2005 1 commit
    • Andrew Morton's avatar
      [PATCH] swabb.h warning fixes · 05133fc4
      Andrew Morton authored
      In file included from drivers/media/dvb/ttpci/av7110_hw.c:38:
      include/linux/byteorder/swabb.h:96: warning: type qualifiers ignored on function return type
      include/linux/byteorder/swabb.h:110: warning: type qualifiers ignored on function return type
      In file included from drivers/media/dvb/ttpci/av7110_v4l.c:36:
      include/linux/byteorder/swabb.h:96: warning: type qualifiers ignored on function return type
      include/linux/byteorder/swabb.h:110: warning: type qualifiers ignored on function return type
      In file included from drivers/media/dvb/ttpci/av7110_av.c:37:
      include/linux/byteorder/swabb.h:96: warning: type qualifiers ignored on function return type
      include/linux/byteorder/swabb.h:110: warning: type qualifiers ignored on function return type
      drivers/isdn/icn/icn.c:719:4: warning: #warning TODO test headroom or use skb->nb to flag ACK
      In file included from drivers/media/dvb/ttpci/av7110_ca.c:39:
      include/linux/byteorder/swabb.h:96: warning: type qualifiers ignored on function return type
      include/linux/byteorder/swabb.h:110: warning: type qualifiers ignored on function return type
      In file included from drivers/media/dvb/ttpci/av7110.c:41:
      include/linux/byteorder/swabb.h:96: warning: type qualifiers ignored on function return type
      include/linux/byteorder/swabb.h:110: warning: type qualifiers ignored on function return type
      
      Does declaring a function to return a const value actually mean something to
      gcc?
      
      Dunno.  Kill it and replace sone `__inline__'s with `inline' too.
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      05133fc4
  23. 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