From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mike Rapoport <rppt@linux.ibm.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 1/2] mm/mmzone.h: fix existing kernel-doc comments and link them to core-api
Date: Mon, 26 Apr 2021 10:36:07 +0530 [thread overview]
Message-ID: <6eddc206-4653-d3c8-3bcb-e92cf4738504@arm.com> (raw)
In-Reply-To: <20210423203811.1247508-2-rppt@kernel.org>
On 4/24/21 2:08 AM, Mike Rapoport wrote:
> From: Mike Rapoport <rppt@linux.ibm.com>
>
> There are a couple of kernel-doc comments in include/linux/mmzone.h but
> they have minor formatting issues that would cause kernel-doc warnings.
>
> Fix the formatting of those comments, add missing Return: descriptions and
> link include/linux/mmzone.h to Documentation/core-api/mm-api.rst
>
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> Documentation/core-api/mm-api.rst | 2 ++
> include/linux/mmzone.h | 43 +++++++++++++++++--------------
> 2 files changed, 26 insertions(+), 19 deletions(-)
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
next prev parent reply other threads:[~2021-04-26 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 20:38 [PATCH 0/2] mmzone.h: fix kernel-doc and simplify is_highmem_idx Mike Rapoport
2021-04-23 20:38 ` [PATCH 1/2] mm/mmzone.h: fix existing kernel-doc comments and link them to core-api Mike Rapoport
2021-04-24 0:08 ` Matthew Wilcox
2021-04-26 5:06 ` Anshuman Khandual [this message]
2021-04-23 20:38 ` [PATCH 2/2] mm/mmzone.h: simplify is_highmem_idx() Mike Rapoport
2021-04-26 6:19 ` Anshuman Khandual
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=6eddc206-4653-d3c8-3bcb-e92cf4738504@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.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).