From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Yury Norov <yury.norov@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Akira Yokosawa <akiyks@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/2] docs: core-api: Update kernel-api.rst to include cpumask.h
Date: Fri, 7 Mar 2025 13:04:50 +0530 [thread overview]
Message-ID: <cover.1741332579.git.viresh.kumar@linaro.org> (raw)
Hello,
This includes cpumask.h in kernel-api.rst and fixes some kernel-doc formatting
warnings/errors.
V2:
- Don't escape *, use @ instead before argument name.
- Don't escape %, use space before "[".
- Use "::" instead of fancy code-blocks.
Viresh Kumar (2):
cpumask: Fix kernel-doc formatting errors in cpumask.h
docs: core-api: Update kernel-api.rst to include cpumask.h
Documentation/core-api/kernel-api.rst | 6 +++
include/linux/cpumask.h | 65 ++++++++++++++-------------
2 files changed, 40 insertions(+), 31 deletions(-)
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2025-03-07 7:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 7:34 Viresh Kumar [this message]
2025-03-07 7:34 ` [PATCH V2 1/2] cpumask: Fix kernel-doc formatting errors in cpumask.h Viresh Kumar
2025-03-07 9:02 ` Akira Yokosawa
2025-03-07 10:57 ` Akira Yokosawa
2025-03-07 11:28 ` Viresh Kumar
2025-03-07 11:20 ` Akira Yokosawa
2025-03-07 17:05 ` Yury Norov
2025-03-10 6:15 ` Viresh Kumar
2025-03-10 9:03 ` Viresh Kumar
2025-03-10 9:29 ` Akira Yokosawa
2025-03-10 9:11 ` Akira Yokosawa
2025-03-10 14:07 ` Jonathan Corbet
2025-03-10 14:43 ` Mauro Carvalho Chehab
2025-03-17 9:24 ` Viresh Kumar
2025-03-10 14:53 ` Mauro Carvalho Chehab
2025-03-10 15:27 ` Akira Yokosawa
2025-03-10 15:56 ` Mauro Carvalho Chehab
2025-03-17 8:53 ` Viresh Kumar
2025-03-07 7:34 ` [PATCH V2 2/2] docs: core-api: Update kernel-api.rst to include cpumask.h Viresh Kumar
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=cover.1741332579.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=vincent.guittot@linaro.org \
--cc=yury.norov@gmail.com \
/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).