1. 07 1月, 2018 1 次提交
  2. 12 12月, 2017 1 次提交
    • T
      doc: add maintainer book · 9727a014
      Tobin C. Harding 提交于
      There is currently very little documentation in the kernel on maintainer
      level tasks. In particular there are no documents on creating pull
      requests to submit to Linus.
      
      Quoting Greg Kroah-Hartman on LKML:
      
          Anyway, this actually came up at the kernel summit / maintainer
          meeting a few weeks ago, in that "how do I make a
          good pull request to Linus" is something we need to document.
      
          Here's what I do, and it seems to work well, so maybe we should turn
          it into the start of the documentation for how to do it.
      
      (quote references: kernel summit, Europe 2017)
      
      Create a new kernel documentation book 'how to be a maintainer'
      (suggested by Jonathan Corbet). Add chapters on 'configuring git' and
      'creating a pull request'.
      
      Most of the content was written by Linus Torvalds and Greg Kroah-Hartman
      in discussion on LKML. This is stated at the start of one of the
      chapters and the original email thread is referenced in
      'pull-requests.rst'.
      Signed-off-by: NTobin C. Harding <me@tobin.cc>
      Reviewed-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Reviewed-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      9727a014
  3. 24 6月, 2017 1 次提交
  4. 16 5月, 2017 4 次提交
  5. 10 5月, 2017 1 次提交
  6. 09 4月, 2017 1 次提交
  7. 03 4月, 2017 1 次提交
  8. 27 1月, 2017 1 次提交
  9. 14 12月, 2016 1 次提交
  10. 30 11月, 2016 1 次提交
  11. 20 11月, 2016 1 次提交
  12. 14 11月, 2016 1 次提交
  13. 11 11月, 2016 1 次提交
    • T
      ALSA: doc: ReSTize alsa-driver-api document · 8551914a
      Takashi Iwai 提交于
      A simple conversion of alsa-driver-api document from DocBook to ReST.
      
      It's moved to the new Documentation/sound/kernel-api subdirectory that
      will contain other ALSA kernel API documents.
      
      The GPL legal note was removed, as it's superfluous (and doesn't fit
      with ReST kernel docs pretty well).
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      8551914a
  14. 08 11月, 2016 2 次提交
  15. 29 10月, 2016 1 次提交
  16. 28 10月, 2016 1 次提交
  17. 27 10月, 2016 1 次提交
  18. 24 10月, 2016 2 次提交
  19. 12 10月, 2016 1 次提交
  20. 21 9月, 2016 1 次提交
  21. 23 8月, 2016 2 次提交
  22. 19 8月, 2016 2 次提交
  23. 15 8月, 2016 1 次提交
  24. 19 7月, 2016 1 次提交
  25. 18 7月, 2016 3 次提交
  26. 08 7月, 2016 1 次提交
  27. 01 7月, 2016 1 次提交
  28. 24 6月, 2016 1 次提交
  29. 23 6月, 2016 1 次提交
  30. 21 6月, 2016 1 次提交
  31. 30 5月, 2016 1 次提交
    • J
      Documentation/sphinx: add basic working Sphinx configuration and build · 22cba31b
      Jani Nikula 提交于
      Add basic configuration and makefile to build documentation from any
      .rst files under Documentation using Sphinx. For starters, there's just
      the placeholder index.rst.
      
      At the top level Makefile, hook Sphinx documentation targets alongside
      (but independent of) the DocBook toolchain, having both be run on the
      various 'make *docs' targets.
      
      All Sphinx processing is placed into Documentation/Makefile.sphinx. Both
      that and the Documentation/DocBook/Makefile are now expected to handle
      all the documentation targets, explicitly ignoring them if they're not
      relevant for that particular toolchain. The changes to the existing
      DocBook Makefile are kept minimal.
      
      There is graceful handling of missing Sphinx and rst2pdf (which is
      needed for pdf output) by checking for the tool and python module,
      respectively, with informative messages to the user.
      
      If the Read the Docs theme (sphinx_rtd_theme) is available, use it, but
      otherwise gracefully fall back to the Sphinx default theme, with an
      informative message to the user, and slightly less pretty HTML output.
      
      Sphinx can now handle htmldocs, pdfdocs (if rst2pdf is available),
      epubdocs and xmldocs targets. The output documents are written into per
      output type subdirectories under Documentation/output.
      
      Finally, you can pass options to sphinx-build using the SPHINXBUILD make
      variable. For example, 'make SPHINXOPTS=-v htmldocs' for more verbose
      output from Sphinx.
      
      This is based on the original work by Jonathan Corbet, but he probably
      wouldn't recognize this as his own anymore.
      Signed-off-by: NJani Nikula <jani.nikula@intel.com>
      22cba31b