linux-kernel.vger.kernel.org archive mirror
 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] A handful of docs fixes
Date: Sat, 4 Mar 2017 08:06:54 -0700	[thread overview]
Message-ID: <20170304080654.43277b0d@lwn.net> (raw)

The following changes since commit
bd8562626c8e170691d6457fe4e8dfb45607a48d:

  docs / driver-api: Fix structure references in device_link.rst (2017-02-20 16:40:46 -0700)

are available in the git repository at:

  git://git.lwn.net/linux.git tags/docs-4.11-fixes

for you to fetch changes up to fd5d666932d51b2552ecc0280047d6b35d9b6cd1:

  Documentation/sphinx: fix primary_domain configuration (2017-03-03 16:12:30 -0700)

----------------------------------------------------------------
A few fixes for the docs tree, including one for a 4.11 build regression.

----------------------------------------------------------------
Cao jin (1):
      pcieaer doc: update the link

John Keeping (1):
      Documentation/sphinx: fix primary_domain configuration

Krzysztof Kozlowski (1):
      Documentation: Update path to sysrq.txt

Martyn Welch (1):
      docs: Fix htmldocs build failure

SeongJae Park (1):
      doc/ko_KR/memory-barriers: Update control-dependencies section

 Documentation/DocBook/Makefile                     |  4 +-
 Documentation/PCI/pcieaer-howto.txt                |  2 +-
 Documentation/conf.py                              |  2 +-
 Documentation/media/v4l-drivers/bttv.rst           |  2 +-
 Documentation/s390/Debugging390.txt                |  2 +-
 Documentation/sysctl/kernel.txt                    |  2 +-
 .../translations/ko_KR/memory-barriers.txt         | 68 ++++++++++++----------
 Documentation/virtual/uml/UserModeLinux-HOWTO.txt  |  6 +-
 8 files changed, 47 insertions(+), 41 deletions(-)

                 reply	other threads:[~2017-03-04 15:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170304080654.43277b0d@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;
as well as URLs for NNTP newsgroup(s).