From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: outreachy@lists.linux.dev
Subject: Re: [PATCH] Documentation/vm: Include kernel-doc from highmem-internal.h
Date: Tue, 19 Apr 2022 14:50:22 +0200 [thread overview]
Message-ID: <7371421.EvYhyI6sBW@leap> (raw)
In-Reply-To: <2824835.e9J7NaK4W3@leap>
On martedì 19 aprile 2022 14:35:48 CEST Fabio M. De Francesco wrote:
> On lunedì 18 aprile 2022 23:36:49 CEST Ira Weiny wrote:
> > 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.
No, I'm a bit distracted and I remembered it badly :(
This patch is already here at
https://lore.kernel.org/outreachy/20220418175638.30018-1-fmdefrancesco@gmail.com/
Fabio
> 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.
next prev parent reply other threads:[~2022-04-19 12:50 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
2022-04-19 12:50 ` Fabio M. De Francesco [this message]
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=7371421.EvYhyI6sBW@leap \
--to=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=outreachy@lists.linux.dev \
/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.