1. 27 12月, 2019 2 次提交
  2. 20 12月, 2018 1 次提交
  3. 08 12月, 2018 1 次提交
  4. 06 12月, 2018 1 次提交
  5. 27 11月, 2018 2 次提交
    • G
      Revert "scripts/setlocalversion: git: Make -dirty check more robust" · 62b5dea3
      Guenter Roeck 提交于
      [ Upstream commit 8ef14c2c41d962756d314f1d7dc972b0ea7a180f ]
      
      This reverts commit 6147b1cf.
      
      The reverted patch results in attempted write access to the source
      repository, even if that repository is mounted read-only.
      
      Output from "strace git status -uno --porcelain":
      
      getcwd("/tmp/linux-test", 129)          = 16
      open("/tmp/linux-test/.git/index.lock", O_RDWR|O_CREAT|O_EXCL|O_CLOEXEC, 0666) =
      	-1 EROFS (Read-only file system)
      
      While git appears to be able to handle this situation, a monitored
      build environment (such as the one used for Chrome OS kernel builds)
      may detect it and bail out with an access violation error. On top of
      that, the attempted write access suggests that git _will_ write to the
      file even if a build output directory is specified. Users may have the
      reasonable expectation that the source repository remains untouched in
      that situation.
      
      Fixes: 6147b1cf ("scripts/setlocalversion: git: Make -dirty check more robust"
      Cc: Genki Sky <sky@genki.is>
      Signed-off-by: NGuenter Roeck <linux@roeck-us.net>
      Reviewed-by: NBrian Norris <briannorris@chromium.org>
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Signed-off-by: NSasha Levin <sashal@kernel.org>
      62b5dea3
    • M
      kbuild: deb-pkg: fix too low build version number · 4d17f22e
      Masahiro Yamada 提交于
      [ Upstream commit bbcde0a7241261cd0ca8d8e6b94a4113a4b71443 ]
      
      Since commit b41d920a ("kbuild: deb-pkg: split generating packaging
      and build"), the build version of the kernel contained in a deb package
      is too low by 1.
      
      Prior to the bad commit, the kernel was built first, then the number
      in .version file was read out, and written into the debian control file.
      
      Now, the debian control file is created before the kernel is actually
      compiled, which is causing the version number mismatch.
      
      Let the mkdebian script pass KBUILD_BUILD_VERSION=${revision} to require
      the build system to use the specified version number.
      
      Fixes: b41d920a ("kbuild: deb-pkg: split generating packaging and build")
      Reported-by: NDoug Smythies <dsmythies@telus.net>
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Tested-by: NDoug Smythies <dsmythies@telus.net>
      Signed-off-by: NSasha Levin <sashal@kernel.org>
      4d17f22e
  6. 21 11月, 2018 1 次提交
  7. 19 9月, 2018 1 次提交
  8. 09 9月, 2018 1 次提交
  9. 05 9月, 2018 3 次提交
  10. 04 9月, 2018 1 次提交
  11. 03 9月, 2018 2 次提交
    • R
      kbuild: make missing $DEPMOD a Warning instead of an Error · 914b087f
      Randy Dunlap 提交于
      When $DEPMOD is not found, only print a warning instead of exiting
      with an error message and error status:
      
      Warning: 'make modules_install' requires /sbin/depmod. Please install it.
      This is probably in the kmod package.
      
      Change the Error to a Warning because "not all build hosts for cross
      compiling Linux are Linux systems and are able to provide a working
      port of depmod, especially at the file patch /sbin/depmod."
      
      I.e., "make modules_install" may be used to copy/install the
      loadable modules files to a target directory on a build system and
      then transferred to an embedded device where /sbin/depmod is run
      instead of it being run on the build system.
      
      Fixes: 934193a6 ("kbuild: verify that $DEPMOD is installed")
      Signed-off-by: NRandy Dunlap <rdunlap@infradead.org>
      Reported-by: NH. Nikolaus Schaller <hns@goldelico.com>
      Cc: stable@vger.kernel.org
      Cc: Lucas De Marchi <lucas.demarchi@profusion.mobi>
      Cc: Lucas De Marchi <lucas.de.marchi@gmail.com>
      Cc: Michal Marek <michal.lkml@markovi.net>
      Cc: Jessica Yu <jeyu@kernel.org>
      Cc: Chih-Wei Huang <cwhuang@linux.org.tw>
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      914b087f
    • M
      kconfig: do not require pkg-config on make {menu,n}config · fd65465b
      Masahiro Yamada 提交于
      Meelis Roos reported a {menu,n}config regression:
       "I have libncurses devel package installed in the default system
        location (as do 99%+ on actual developers probably) and in this
        case, pkg-config is useless.  pkg-config is needed only when
        libraries and headers are installed in non-default locations but
        it is bad to require installation of pkg-config on all the machines
        where make menuconfig would be possibly run."
      
      For {menu,n}config, do not use pkg-config if it is not installed.
      For {g,x}config, keep checking pkg-config since we really rely on it
      for finding the installation paths of the required packages.
      
      Fixes: 4ab3b801 ("kconfig: check for pkg-config on make {menu,n,g,x}config")
      Reported-by: NMeelis Roos <mroos@linux.ee>
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Tested-by: NMeelis Roos <mroos@linux.ee>
      Tested-by: NRandy Dunlap <rdunlap@infradead.org>
      fd65465b
  12. 01 9月, 2018 2 次提交
  13. 30 8月, 2018 2 次提交
  14. 24 8月, 2018 4 次提交
  15. 23 8月, 2018 16 次提交