1. 02 2月, 2018 1 次提交
    • K
      Documentation/process: kernel maintainer PGP guide · b72dde38
      Konstantin Ryabitsev 提交于
      This guide is an adapted version of the more general "Protecting Code
      Integrity" guide written and maintained by The Linux Foundation IT for
      use with open-source projects. It provides the oft-lacking guidance on
      the following topics:
      
      - how to properly protect one's PGP keys to minimize the risks of them
        being stolen and used maliciously to impersonate a kernel developer
      - how to configure Git to properly use GnuPG
      - when and how to use PGP with Git
      - how to verify fellow Linux Kernel developer identities
      
      I believe this document should live with the rest of the documentation
      describing proper processes one should follow when participating in
      kernel development. Placing it in a wiki on some place like kernel.org
      would be insufficient for a number of reasons -- primarily, because only
      a relatively small subset of maintainers have accounts on kernel.org,
      but also because even those who do rarely remember that such wiki
      exists. Keeping it with the rest of in-kernel docs should hopefully give
      it more visibility, but also help keep it up-to-date as tools and
      processes evolve.
      Signed-off-by: NKonstantin Ryabitsev <konstantin@linuxfoundation.org>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      b72dde38
  2. 07 1月, 2018 1 次提交
  3. 22 12月, 2017 4 次提交
  4. 12 12月, 2017 1 次提交
  5. 30 11月, 2017 1 次提交
  6. 21 11月, 2017 1 次提交
  7. 04 11月, 2017 2 次提交
  8. 03 11月, 2017 1 次提交
  9. 23 10月, 2017 1 次提交
  10. 21 10月, 2017 2 次提交
  11. 20 10月, 2017 2 次提交
  12. 19 10月, 2017 5 次提交
  13. 16 10月, 2017 1 次提交
  14. 13 10月, 2017 1 次提交
  15. 08 10月, 2017 1 次提交
  16. 27 9月, 2017 2 次提交
  17. 31 8月, 2017 1 次提交
  18. 25 8月, 2017 1 次提交
  19. 24 7月, 2017 1 次提交
  20. 18 7月, 2017 2 次提交
  21. 30 6月, 2017 1 次提交
  22. 23 6月, 2017 1 次提交
  23. 06 6月, 2017 1 次提交
  24. 16 5月, 2017 1 次提交
  25. 07 5月, 2017 2 次提交
    • M
      docs: complete bumping minimal GNU Make version to 3.81 · 13e09881
      Max Filippov 提交于
      Commit 37d69ee3 ("docs: bump minimal GNU Make version to 3.81")
      changes one entry of GNU make version in the changes.rst, there's still
      one more entry saying that one need version 3.80.  Fix that.
      Signed-off-by: NMax Filippov <jcmvbkbc@gmail.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      13e09881
    • M
      docs: bump minimal GNU Make version to 3.81 · 37d69ee3
      Masahiro Yamada 提交于
      Since 2014, you can't successfully build kernels with GNU Make version
      3.80. Example errors:
      
        $ git describe
        v4.11
        $ make --version | head -1
        GNU Make 3.80
        $ make defconfig
          HOSTCC  scripts/basic/fixdep
        scripts/Makefile.host:135: *** missing separator.  Stop.
        make: *** [defconfig] Error 2
        $ make ARCH=arm64 help
        arch/arm64/Makefile:43: *** unterminated call to function `warning': missing `)'.  Stop.
        $ make help >/dev/null
        ./Documentation/Makefile.sphinx:25: Extraneous text after `else' directive
        ./Documentation/Makefile.sphinx:31: *** only one `else' per conditional.  Stop.
        make: *** [help] Error 2
      
      The first breakage was introduced by commit c8589d1e ("kbuild:
      handle multi-objs dependency appropriately").  Since then (i.e. v3.18),
      GNU Make 3.80 has not been able to compile the kernel, but nobody has
      ever complained aboutt (or noticed) it.
      
      Even GNU Make 3.81 is more than 10 years old.  It would not hurt to
      match the documentation with reality instead of fixing makefiles.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      37d69ee3
  26. 21 4月, 2017 1 次提交
  27. 09 4月, 2017 1 次提交
    • J
      Documentation: stable-kernel-rules: fix stable-tag format · 9581539e
      Johan Hovold 提交于
      A patch documenting how to specify which kernels a particular fix should
      be backported to (seemingly) inadvertently added a minus sign after the
      kernel version. This particular stable-tag format had never been used
      prior to this patch, and was neither present when the patch in question
      was first submitted (it was added in v2 without any comment).
      
      Drop the minus sign to avoid any confusion.
      
      Fixes: fdc81b79 ("stable_kernel_rules: Add clause about specification of kernel versions to patch.")
      Signed-off-by: NJohan Hovold <johan@kernel.org>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      9581539e