[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2024072335-gills-washtub-35a9@gregkh>
Date: Tue, 23 Jul 2024 14:15:50 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: SeongJae Park <sj@...nel.org>
Cc: stable@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...hat.com>,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
Steven Rostedt <rostedt@...dmis.org>, damon@...ts.linux.dev,
linux-mm@...ck.org, linux-sparse@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5.15.y 0/8] Backport patches for DAMON merge regions fix
On Tue, Jul 16, 2024 at 11:33:25AM -0700, SeongJae Park wrote:
> Commit 310d6c15e910 ("mm/damon/core: merge regions aggressively when
> max_nr_regions") causes a build warning and a build failure [1] on
> 5.15.y. Those are due to
> 1) unnecessarily strict type check from max(), and
> 2) use of not-yet-introduced damon_ctx->attrs field, respectively.
>
> Fix the warning by backporting a minmax.h upstream commit that made the
> type check less strict for unnecessary case, and upstream commits that
> it depends on.
>
> Note that all patches except the fourth one ("minmax: fix header
> inclusions") are clean cherry-picks of upstream commit. For the fourth
> one, minor conflict resolving was needed.
>
> Also, the last patch, which is the backport of the DAMON fix, was
> cleanly cherry-picked, but added manual fix for the build failure.
>
> [1] https://lore.kernel.org/2024071532-pebble-jailhouse-48b2@gregkh
All now queued up, again, thank you for the minmax backports, much
appreciated.
greg k-h
Powered by blists - more mailing lists