From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
SeongJae Park <sj@kernel.org>,
Jiajian Ye <yejiajian2018@email.szu.edu.cn>,
Thomas Gleixner <tglx@linutronix.de>,
Matthew Wilcox <willy@infradead.org>,
Peter Zijlstra <peterz@infradead.org>,
outreachy@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/vm: Include kernel-doc from highmem-internal.h
Date: Tue, 19 Apr 2022 14:35:48 +0200 [thread overview]
Message-ID: <2824835.e9J7NaK4W3@leap> (raw)
In-Reply-To: <Yl3Z8Qll+zGo4v/D@iweiny-desk3>
On lunedì 18 aprile 2022 23:36:49 CEST Ira Weiny wrote:
> On Mon, Apr 18, 2022 at 10:17:40AM +0200, Fabio M. De Francesco wrote:
> > In Documentation/vm/highmem.rst the kernel-doc comments are missing,
> > therefore kunmap_local() and kunmap_atomic() are yet undocumented.
> >
> > Add a kernel-doc directive to include the above-mentioned kernel-doc
> > comments in highmem.rst.
> >
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Ira Weiny <ira.weiny@intel.com>
> > Cc: Matthew Wilcox <willy@infradead.org>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
>
> I thought I saw a patch fly by which changed the comment of
kunmap_atomic() in
> include/linux/highmem-internal.h? Did I miss that somewhere?
Sorry, in my other email I responded after misunderstanding your question
because I had just noticed a typo so that I had something else in my mind.
It looks that you are talking about the following patch and, if so, you saw
it correctly:
"[PATCH v2] mm/highmem: Fix kernel-doc warnings in highmem*.h" at
https://lore.kernel.org/lkml/20220418175638.30018-1-fmdefrancesco@gmail.com/
I forgot to send it to the Outreachy list. I'm about to resend it only to
this list in order to make Outreachy's organizers to know about it. For v1
already had an "Acked-by:" tag from Mike Rapoport.
Thanks,
Fabio M. De Francesco
next prev parent reply other threads:[~2022-04-19 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 8:17 [PATCH] Documentation/vm: Include kernel-doc from highmem-internal.h Fabio M. De Francesco
2022-04-18 21:36 ` Ira Weiny
2022-04-18 22:05 ` Fabio M. De Francesco
2022-04-19 12:35 ` Fabio M. De Francesco [this message]
2022-04-19 12:50 ` Fabio M. De Francesco
2022-04-21 17:52 ` Fabio M. De Francesco
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=2824835.e9J7NaK4W3@leap \
--to=fmdefrancesco@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=sj@kernel.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=yejiajian2018@email.szu.edu.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.