From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-doc@vger.kernel.org
Subject: [GIT PULL] Documentation fixes for 5.14
Date: Fri, 16 Jul 2021 12:33:54 -0600 [thread overview]
Message-ID: <87fsweds6l.fsf@meer.lwn.net> (raw)
The following changes since commit e73f0f0ee7541171d89f2e2491130c7771ba58d3:
Linux 5.14-rc1 (2021-07-11 15:07:40 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.14-2
for you to fetch changes up to 530c4374e21ae750c5fa5aa67b36a97635ddb379:
docs/zh_CN: add a missing space character (2021-07-15 06:33:44 -0600)
----------------------------------------------------------------
A handful of fixes in and around documentation. Some funky quotes in
LICENSES/dual/CC-BY-4.0 were giving spdxcheck.py grief; that has been
fixed on both ends. Also a couple of features updates and one docs
build fix.
----------------------------------------------------------------
Hu Haowen (1):
docs/zh_CN: add a missing space character
Ingo Molnar (2):
Documentation/features: Update the ARCH_HAS_TICK_BROADCAST entry
Documentation/features: Add THREAD_INFO_IN_TASK feature matrix
Nishanth Menon (2):
scripts/spdxcheck.py: Strictly read license files in utf-8
LICENSES/dual/CC-BY-4.0: Git rid of "smart quotes"
.../core/thread-info-in-task/arch-support.txt | 32 ++++++++++++++++++++++
.../time/arch-tick-broadcast/arch-support.txt | 2 +-
.../translations/zh_CN/process/2.Process.rst | 4 +--
LICENSES/dual/CC-BY-4.0 | 2 +-
scripts/spdxcheck.py | 2 +-
5 files changed, 37 insertions(+), 5 deletions(-)
create mode 100644 Documentation/features/core/thread-info-in-task/arch-support.txt
next reply other threads:[~2021-07-16 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 18:33 Jonathan Corbet [this message]
2021-07-17 0:54 ` [GIT PULL] Documentation fixes for 5.14 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=87fsweds6l.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.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).