[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2147048.ZfL8zNpBrT@leap>
Date: Tue, 19 Apr 2022 19:13:06 +0200
From: "Fabio M. De Francesco" <fmdefrancesco@...il.com>
To: Ira Weiny <ira.weiny@...el.com>
Cc: Matthew Wilcox <willy@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Peter Collingbourne <pcc@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Mike Rapoport <rppt@...ux.ibm.com>,
linux-kernel@...r.kernel.org, outreachy@...ts.linux.dev
Subject: Re: [PATCH v2] mm/highmem: Fix kernel-doc warnings in highmem*.h
On martedì 19 aprile 2022 17:09:04 CEST Fabio M. De Francesco wrote:
> 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).
No, you are right. There are 4 patches in my queue for Highmem related
files. I think I'm at a point where I'm starting to lose sight of the tasks
due :(
> 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.
The collection of all these patches in one series is confirmed for all 4.
Thanks,
Fabio
Powered by blists - more mailing lists