public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [GIT PULL] Documentation fixes for 5.12
Date: Fri, 26 Feb 2021 11:54:04 -0700	[thread overview]
Message-ID: <87blc68xtf.fsf@meer.lwn.net> (raw)

The following changes since commit 3c2e0a489da6a7c48ad67a246c7a287fcb4a4607:

  docs: kernel-hacking: be more civil (2021-02-11 10:00:40 -0700)

are available in the Git repository at:

  git://git.lwn.net/linux.git tags/docs-5.12-2

for you to fetch changes up to f37a15ea8db022373a2cb6d1a6004c65c2b7f17e:

  docs: proc.rst: fix indentation warning (2021-02-25 13:11:00 -0700)

----------------------------------------------------------------
A handful of late-arriving documentation fixes, nothing all that notable.

----------------------------------------------------------------
Aditya Srivastava (1):
      scripts: kernel-doc: fix array element capture in pointer-to-func parsing

Andrew Donnellan (1):
      docs: powerpc: Fix tables in syscall64-abi.rst

Antonio Terceiro (1):
      Documentation: cgroup-v2: fix path to example BPF program

Arnd Bergmann (2):
      Documentation: features: remove c6x references
      Documentation: features: refresh feature list

Masahiro Yamada (1):
      doc: use KCFLAGS instead of EXTRA_CFLAGS to pass flags from command line

Matthew Wilcox (1):
      Fix unaesthetic indentation

Michael Weiß (1):
      docs: ABI: testing: ima_policy: Fixed missing bracket

Randy Dunlap (2):
      Documentation: proc.rst: add more about the 6 fields in loadavg
      docs: proc.rst: fix indentation warning

 Documentation/ABI/testing/ima_policy               |  2 +-
 Documentation/admin-guide/cgroup-v2.rst            |  2 +-
 Documentation/conf.py                              |  3 +-
 .../features/core/cBPF-JIT/arch-support.txt        |  1 -
 .../features/core/eBPF-JIT/arch-support.txt        |  1 -
 .../core/generic-idle-thread/arch-support.txt      |  1 -
 .../features/core/jump-labels/arch-support.txt     |  1 -
 .../features/core/tracehook/arch-support.txt       |  1 -
 .../features/debug/KASAN/arch-support.txt          |  1 -
 .../debug/debug-vm-pgtable/arch-support.txt        |  1 -
 .../debug/gcov-profile-all/arch-support.txt        |  3 +-
 Documentation/features/debug/kcov/arch-support.txt |  1 -
 Documentation/features/debug/kgdb/arch-support.txt |  1 -
 .../features/debug/kmemleak/arch-support.txt       |  3 +-
 .../debug/kprobes-on-ftrace/arch-support.txt       |  3 +-
 .../features/debug/kprobes/arch-support.txt        |  3 +-
 .../features/debug/kretprobes/arch-support.txt     |  3 +-
 .../features/debug/optprobes/arch-support.txt      |  1 -
 .../features/debug/stackprotector/arch-support.txt |  1 -
 .../features/debug/uprobes/arch-support.txt        |  3 +-
 .../debug/user-ret-profiler/arch-support.txt       |  1 -
 .../features/io/dma-contiguous/arch-support.txt    |  1 -
 .../locking/cmpxchg-local/arch-support.txt         |  1 -
 .../features/locking/lockdep/arch-support.txt      |  1 -
 .../locking/queued-rwlocks/arch-support.txt        |  1 -
 .../locking/queued-spinlocks/arch-support.txt      |  1 -
 .../features/perf/kprobes-event/arch-support.txt   |  3 +-
 .../features/perf/perf-regs/arch-support.txt       |  3 +-
 .../features/perf/perf-stackdump/arch-support.txt  |  3 +-
 .../sched/membarrier-sync-core/arch-support.txt    |  1 -
 .../features/sched/numa-balancing/arch-support.txt |  3 +-
 .../seccomp/seccomp-filter/arch-support.txt        |  1 -
 .../time/arch-tick-broadcast/arch-support.txt      |  1 -
 .../features/time/clockevents/arch-support.txt     |  1 -
 .../time/context-tracking/arch-support.txt         |  1 -
 .../features/time/irq-time-acct/arch-support.txt   |  1 -
 .../features/time/virt-cpuacct/arch-support.txt    |  1 -
 .../features/vm/ELF-ASLR/arch-support.txt          |  1 -
 .../features/vm/PG_uncached/arch-support.txt       |  1 -
 Documentation/features/vm/THP/arch-support.txt     |  1 -
 Documentation/features/vm/TLB/arch-support.txt     |  1 -
 .../features/vm/huge-vmap/arch-support.txt         |  1 -
 .../features/vm/ioremap_prot/arch-support.txt      |  1 -
 .../features/vm/pte_special/arch-support.txt       |  1 -
 Documentation/filesystems/proc.rst                 |  4 ++
 Documentation/powerpc/syscall64-abi.rst            | 51 ++++++++++++++--------
 Documentation/process/4.Coding.rst                 |  2 +-
 Documentation/process/submit-checklist.rst         |  2 +-
 .../translations/it_IT/process/4.Coding.rst        |  2 +-
 .../it_IT/process/submit-checklist.rst             |  2 +-
 .../translations/zh_CN/process/4.Coding.rst        |  2 +-
 drivers/gpu/drm/tilcdc/Makefile                    |  2 +-
 scripts/kernel-doc                                 |  2 +-
 53 files changed, 56 insertions(+), 81 deletions(-)

             reply	other threads:[~2021-02-26 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 18:54 Jonathan Corbet [this message]
2021-02-26 22:23 ` [GIT PULL] Documentation fixes for 5.12 pr-tracker-bot

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=87blc68xtf.fsf@meer.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