From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Ira Weiny <ira.weiny@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Will Deacon <will@kernel.org>,
Peter Collingbourne <pcc@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH] mm/highmem: Fix kernel-doc warnings in highmem*.h
Date: Mon, 18 Apr 2022 19:22:44 +0200 [thread overview]
Message-ID: <13023135.uLZWGnKmhe@leap> (raw)
In-Reply-To: <Yl14+RJjFU58yNpR@kernel.org>
On lunedì 18 aprile 2022 16:43:05 CEST Mike Rapoport wrote:
> Hi,
>
> On Mon, Apr 18, 2022 at 09:53:04AM +0200, Fabio M. De Francesco wrote:
> > `scripts/kernel-doc -none include/linux/highmem*` reports the following
> > warnings:
> >
> > include/linux/highmem.h:160: warning: expecting prototype for
kunmap_atomic(). Prototype was for nr_free_highpages() instead
> > include/linux/highmem-internal.h:256: warning: Function parameter or
member '__addr' not described in 'kunmap_atomic'
> > include/linux/highmem-internal.h:256: warning: Excess function
parameter 'addr' description in 'kunmap_atomic'
> >
> > Fix these warnings by (1) move the kernel-doc comments from highmem.h
to
> > highmem-internal.h (which is the file were the kunmap_atomic() macro is
> > actually defined), merge it with the comment which already was in
>
> ^ (2) ?
>
> > highmem-internal.h, and (3) replace "@addr" with "@__addr".
Hi Mike,
It looks like these days I'm a bit distracted...
I'm about to send a v2 patch.
>
> There is also replacement of "addr" with "page", so I'd phrase (3) as
> "use correct parameter names"
Yes, correct, I missed this too :(
>
> > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
>
> Other than that
>
> Acked-by: Mike Rapoport <rppt@linux.ibm.com>
Thanks for your "Acked-by:" tag.
Regards,
Fabio
> > ---
> > include/linux/highmem-internal.h | 14 +++++++++++---
> > include/linux/highmem.h | 13 +------------
> > 2 files changed, 12 insertions(+), 15 deletions(-)
> >
> > [snip]
prev parent reply other threads:[~2022-04-18 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 7:53 [PATCH] mm/highmem: Fix kernel-doc warnings in highmem*.h Fabio M. De Francesco
2022-04-18 14:43 ` Mike Rapoport
2022-04-18 17:22 ` Fabio M. De Francesco [this message]
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=13023135.uLZWGnKmhe@leap \
--to=fmdefrancesco@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=pcc@google.com \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--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