mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-doc@vger.kernel.org
Subject: [PULL] Docs fixes
Date: Fri, 5 Aug 2016 08:59:50 -0600	[thread overview]
Message-ID: <20160805085950.241e1d0a@lwn.net> (raw)

A handful of documentation fixes.  You'll get a conflict on
Documentation/DocBook/Makefile due to the changes from the drm and media
trees.  Resolution is pretty easy - just take the docs-next side - but I
also have a resolution in the docs-next-merge branch if that's useful to
you.

Thanks,

jon

The following changes since commit
a88b1672d4ddf9895eb53e6980926d5e960dea8e:

  doc-rst: kernel-doc: fix handling of address_space tags (2016-07-22 15:34:24 -0600)

are available in the git repository at:

  git://git.lwn.net/linux.git tags/doc-4.8-fixes

for you to fetch changes up to bdf107d87eb8ce1d1313fee40f3de1a1029a3eca:

  DocBook: use DOCBOOKS="" to ignore DocBooks instead of IGNORE_DOCBOOKS=1 (2016-08-04 16:51:33 -0600)

----------------------------------------------------------------
Three fixes for the docs build, including removing an annoying warning on
"make help" if sphinx isn't present.

----------------------------------------------------------------
Jani Nikula (2):
      Documentation/sphinx: do not warn about missing tools in 'make help'
      DocBook: use DOCBOOKS="" to ignore DocBooks instead of IGNORE_DOCBOOKS=1

seokhoon.yoon (1):
      Documenation: update cgroup's document path

 Documentation/DocBook/Makefile                 | 26 ++++++++++----------------
 Documentation/Makefile.sphinx                  |  4 ++--
 Documentation/cgroup-v1/cgroups.txt            |  4 ++--
 Documentation/cgroup-v1/cpusets.txt            |  2 +-
 Documentation/cgroup-v1/memcg_test.txt         |  4 ++--
 Documentation/filesystems/tmpfs.txt            |  2 +-
 Documentation/kernel-parameters.txt            |  4 ++--
 Documentation/kernel-per-CPU-kthreads.txt      |  2 +-
 Documentation/scheduler/sched-deadline.txt     |  2 +-
 Documentation/scheduler/sched-design-CFS.txt   |  2 +-
 Documentation/scheduler/sched-rt-group.txt     |  2 +-
 Documentation/vm/numa                          |  4 ++--
 Documentation/vm/numa_memory_policy.txt        |  2 +-
 Documentation/vm/page_migration                |  2 +-
 Documentation/vm/unevictable-lru.txt           |  2 +-
 Documentation/x86/x86_64/fake-numa-for-cpusets |  4 ++--
 16 files changed, 31 insertions(+), 37 deletions(-)

             reply	other threads:[~2016-08-05 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05 14:59 Jonathan Corbet [this message]
2016-08-18 23:56 Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160805085950.241e1d0a@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®