Merge tag 'docs-4.10' of git://git.lwn.net/linuxHEADmaster

Pull documentation update from Jonathan Corbet:
 "These are the documentation changes for 4.10.

  It's another busy cycle for the docs tree, as the sphinx conversion
  continues. Highlights include:

   - Further work on PDF output, which remains a bit of a pain but
     should be more solid now.

   - Five more DocBook template files converted to Sphinx. Only 27 to
     go... Lots of plain-text files have also been converted and
     integrated.

   - Images in binary formats have been replaced with more
     source-friendly versions.

   - Various bits of organizational work, including the renaming of
     various files discussed at the kernel summit.

   - New documentation for the device_link mechanism.

  ... and, of course, lots of typo fixes and small updates"

* tag 'docs-4.10' of git://git.lwn.net/linux: (193 commits)
  dma-buf: Extract dma-buf.rst
  Update Documentation/00-INDEX
  docs: 00-INDEX: document directories/files with no docs
  docs: 00-INDEX: remove non-existing entries
  docs: 00-INDEX: add missing entries for documentation files/dirs
  docs: 00-INDEX: consolidate process/ and admin-guide/ description
  scripts: add a script to check if Documentation/00-INDEX is sane
  Docs: change sh -> awk in REPORTING-BUGS
  Documentation/core-api/device_link: Add initial documentation
  core-api: remove an unexpected unident
  ppc/idle: Add documentation for powersave=off
  Doc: Correct typo, "Introdution" => "Introduction"
  Documentation/atomic_ops.txt: convert to ReST markup
  Documentation/local_ops.txt: convert to ReST markup
  Documentation/assoc_array.txt: convert to ReST markup
  docs-rst: parse-headers.pl: cleanup the documentation
  docs-rst: fix media cleandocs target
  docs-rst: media/Makefile: reorganize the rules
  docs-rst: media: build SVG from graphviz files
  docs-rst: replace bayer.png by a SVG image
  ...

path: root/REPORTING-BUGS

For reporting bugs send an email to the <netsniff-ng@googlegroups.com> list.

Alternatively, you can create an issue on our Github project:

  * https://github.com/netsniff-ng/netsniff-ng/issues

If you use Fedora or have a RHEL subscription, you can also report bugs to:

  * https://bugzilla.redhat.com/

If you use Debian Linux, we might also process / track bugs there:

  * http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=netsniff-ng

In any way, you'll get a reply from us. Please do not contact individual
developers directly in case of netsniff-ng issues or patches, but rather
always our mailing list. By this, you're not wasting time of a single
developer and increase your chances of getting a reply from us.

In general, we are also highly interested in how you use the toolkit, what
problems you are trying to solve and what kind of things you would like to have
improved. So feel free to drop us some feature requests as well.