From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Matthew Wilcox <willy@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH v2 0/2] mmzone.h: fix kernel-doc and simplify is_highmem_idx
Date: Mon, 26 Apr 2021 17:19:25 +0300 [thread overview]
Message-ID: <20210426141927.1314326-1-rppt@kernel.org> (raw)
From: Mike Rapoport <rppt@linux.ibm.com>
Hi,
There are several kernel-doc comments in include/linux/mmzone.h, but
they have some formatting issues and they are not linked to the rest of
the documentation.
The first patch here fixes the formatting and adds the kernel-doc
comments to the core-api/mm-api.rst.
The second patch simplifies a bit detection if a zone is a highmem zone.
It does not generally depends on the first one, but they have a textual
conflict.
v2:
* rebase on v5.12-rc8-mmots-2021-04-21-23-08
* add Reviewed-by tags, thanks Anshuman and Matthew
v1: Link: /home/mike/tmp/mm-docs/mmzone/v2/v2-0000-cover-letter.patch
Mike Rapoport (2):
mm/mmzone.h: fix existing kernel-doc comments and link them to core-api
mm/mmzone.h: simplify is_highmem_idx()
Documentation/core-api/mm-api.rst | 1 +
include/linux/mmzone.h | 56 ++++++++++++++-----------------
2 files changed, 26 insertions(+), 31 deletions(-)
base-commit: 5770176c2a0eaa998c58cfc7a9a5fe5b9291dd2a
--
2.29.2
next reply other threads:[~2021-04-26 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 14:19 Mike Rapoport [this message]
2021-04-26 14:19 ` [PATCH v2 1/2] mm/mmzone.h: fix existing kernel-doc comments and link them to core-api Mike Rapoport
2021-04-26 14:19 ` [PATCH v2 2/2] mm/mmzone.h: simplify is_highmem_idx() Mike Rapoport
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=20210426141927.1314326-1-rppt@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.com \
--cc=willy@infradead.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).