From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Peter Collingbourne <pcc@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Mike Rapoport <rppt@linux.ibm.com>,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH v2] mm/highmem: Fix kernel-doc warnings in highmem*.h
Date: Tue, 19 Apr 2022 17:09:04 +0200 [thread overview]
Message-ID: <6767543.18pcnM708K@leap> (raw)
In-Reply-To: <Yl7MpmsXtzOfztHu@iweiny-desk3>
On martedì 19 aprile 2022 16:52:22 CEST Ira Weiny wrote:
> On Tue, Apr 19, 2022 at 03:25:16PM +0200, Fabio M. De Francesco wrote:
>
> [snip]
>
> I think you should gather all these patches together into a series and
submit.
> If I am following correctly there are at least 4 patches now? But I'm
unsure
> of which ones are stand alone.
>
> It would be easier to see what changes are being made along the way as
well as
> the final result of the fixes.
>
> Ira
Yes, this is perfectly reasonable. There are only three patches (this patch
plus two more in a series). Since they are all related in some way, it is
best to bring them together into one series which I will rework taking into
account both yours and Matthew's suggestions.
Thanks,
Fabio
next prev parent reply other threads:[~2022-04-19 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 17:56 [PATCH v2] mm/highmem: Fix kernel-doc warnings in highmem*.h Fabio M. De Francesco
2022-04-19 12:44 ` Matthew Wilcox
2022-04-19 13:25 ` Fabio M. De Francesco
2022-04-19 14:52 ` Ira Weiny
2022-04-19 15:09 ` Fabio M. De Francesco [this message]
2022-04-19 17:13 ` Fabio M. De Francesco
2022-04-21 17:50 ` 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=6767543.18pcnM708K@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@linux.ibm.com \
--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 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.