An error occurred fetching the project authors.
  1. 16 Aug, 2017 1 commit
  2. 13 Aug, 2017 1 commit
  3. 11 Aug, 2017 1 commit
  4. 06 Aug, 2017 1 commit
  5. 27 Jul, 2017 2 commits
    • Greg Kroah-Hartman's avatar
      Linux 4.12.4 · 13df91db
      Greg Kroah-Hartman authored
      13df91db
    • Linus Torvalds's avatar
      disable new gcc-7.1.1 warnings for now · e346433d
      Linus Torvalds authored
      commit bd664f6b upstream.
      
      I made the mistake of upgrading my desktop to the new Fedora 26 that
      comes with gcc-7.1.1.
      
      There's nothing wrong per se that I've noticed, but I now have 1500
      lines of warnings, mostly from the new format-truncation warning
      triggering all over the tree.
      
      We use 'snprintf()' and friends in a lot of places, and often know that
      the numbers are fairly small (ie a controller index or similar), but gcc
      doesn't know that, and sees an 'int', and thinks that it could be some
      huge number.  And then complains when our buffers are not able to fit
      the name for the ten millionth controller.
      
      These warnings aren't necessarily bad per se, and we probably want to
      look through them subsystem by subsystem, but at least during the merge
      window they just mean that I can't even see if somebody is introducing
      any *real* problems when I pull.
      
      So warnings disabled for now.
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      e346433d
  6. 21 Jul, 2017 1 commit
  7. 15 Jul, 2017 1 commit
  8. 12 Jul, 2017 1 commit
  9. 02 Jul, 2017 1 commit
  10. 26 Jun, 2017 1 commit
  11. 19 Jun, 2017 1 commit
  12. 11 Jun, 2017 1 commit
  13. 06 Jun, 2017 1 commit
  14. 04 Jun, 2017 1 commit
  15. 29 May, 2017 1 commit
  16. 22 May, 2017 1 commit
  17. 17 May, 2017 1 commit
    • Masahiro Yamada's avatar
      kbuild: skip install/check of headers right under uapi directories · 05d8cba4
      Masahiro Yamada authored
      Since commit 61562f98 ("uapi: export all arch specifics
      directories"), "make INSTALL_HDR_PATH=$root/usr headers_install"
      deletes standard glibc headers and others in $(root)/usr/include.
      
      The cause of the issue is that headers_install now starts descending
      from arch/$(hdr-arch)/include/uapi with $(root)/usr/include for its
      destination when installing asm headers.  So, headers already there
      are assumed to be unwanted.
      
      When headers_install starts descending from include/uapi with
      $(root)/usr/include for its destination, it works around the problem
      by creating an dummy destination $(root)/usr/include/uapi, but this
      is tricky.
      
      To fix the problem in a clean way is to skip headers install/check
      in include/uapi and arch/$(hdr-arch)/include/uapi because we know
      there are only sub-directories in uapi directories.  A good side
      effect is the empty destination $(root)/usr/include/uapi will go
      away.
      
      I am also removing the trailing slash in the headers_check target to
      skip checking in arch/$(hdr-arch)/include/uapi.
      
      Fixes: 61562f98 ("uapi: export all arch specifics directories")
      Reported-by: default avatarDan Williams <dan.j.williams@intel.com>
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Tested-by: default avatarDan Williams <dan.j.williams@intel.com>
      Acked-by: default avatarNicolas Dichtel <nicolas.dichtel@6wind.com>
      05d8cba4
  18. 13 May, 2017 1 commit
  19. 10 May, 2017 1 commit
  20. 09 May, 2017 1 commit
  21. 03 May, 2017 1 commit
  22. 01 May, 2017 1 commit
  23. 28 Apr, 2017 1 commit
  24. 24 Apr, 2017 1 commit
  25. 23 Apr, 2017 3 commits
  26. 18 Apr, 2017 1 commit
    • Masahiro Yamada's avatar
      kbuild: avoid conflict between -ffunction-sections and -pg on gcc-4.7 · 90ad4052
      Masahiro Yamada authored
      Arnd Bergmann reported:
        "When ftrace is enabled and we build with gcc-4.7 or older, we
        get a warning for each file on architectures that select
        CONFIG_LD_DEAD_CODE_DATA_ELIMINATION:
      
        warning: -ffunction-sections disabled; it makes profiling impossible [enabled by default]
        "
      
      Since commit c3f0d0bc ("kbuild, LLVMLinux: Add -Werror to
      cc-option to support clang"), warnings are treated as errors in
      cc-option checks.  CC_FLAGS_FTRACE is blindly added to KBUILD_CFLAGS,
      so $(call cc-option,-ffunction-sections,) should be moved below it
      in order to detect the conflict between the two options.
      Reported-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      90ad4052
  27. 16 Apr, 2017 1 commit
  28. 12 Apr, 2017 1 commit
  29. 09 Apr, 2017 1 commit
  30. 03 Apr, 2017 1 commit
  31. 31 Mar, 2017 1 commit
  32. 26 Mar, 2017 1 commit
  33. 21 Mar, 2017 2 commits
  34. 20 Mar, 2017 1 commit
  35. 16 Mar, 2017 1 commit
    • Arnd Bergmann's avatar
      Kbuild: use cc-disable-warning consistently for maybe-uninitialized · b334e19a
      Arnd Bergmann authored
      In commit a76bcf55 ("Kbuild: enable -Wmaybe-uninitialized warning
      for "make W=1""), I reverted another change that happened to fix a problem
      with old compilers, and now we get this report again with old compilers
      (prior to gcc-4.8) and GCOV enabled:
      
         cc1: warnings being treated as errors
         drivers/gpu/drm/i915/intel_ringbuffer.c: In function 'intel_ring_setup_status_page':
         drivers/gpu/drm/i915/intel_ringbuffer.c:438: error: 'mmio.reg' may be used uninitialized in this function
         At top level:
      >> cc1: error: unrecognized command line option "-Wno-maybe-uninitialized"
      
      The problem is that we turn off the warning conditionally in a number
      of places as we should, but one of them does it unconditionally.
      Instead, change it to call cc-disable-warning as we do elsewhere.
      
      The original patch that caused it was merged into linux-4.7, then
      4.8 removed the change and 4.9 brought it back, so we probably want
      a backport to 4.9 once this is merged.
      
      Use a ':=' assignment instead of '=' to force the cc-disable-warning
      call to only be evaluated once instead of every time.
      
      Cc: stable@vger.kernel.org
      Fixes: a76bcf55 ("Kbuild: enable -Wmaybe-uninitialized warning for "make W=1"")
      Fixes: e72e2dfe ("gcov: disable -Wmaybe-uninitialized warning")
      Reported-by: default avatarkbuild test robot <fengguang.wu@intel.com>
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      b334e19a
  36. 14 Mar, 2017 1 commit