From: Greg KH <gregkh@linuxfoundation.org>
To: SeongJae Park <sj@kernel.org>
Cc: stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1.y 0/7] Backport patches for DAMON merge regions fix
Date: Tue, 23 Jul 2024 14:10:33 +0200 [thread overview]
Message-ID: <2024072352-override-creasing-a0aa@gregkh> (raw)
In-Reply-To: <2024071624-mustiness-quarterly-f34e@gregkh>
On Tue, Jul 16, 2024 at 08:23:46PM +0200, Greg KH wrote:
> On Tue, Jul 16, 2024 at 10:51:58AM -0700, SeongJae Park wrote:
> > Commit 310d6c15e910 ("mm/damon/core: merge regions aggressively when
> > max_nr_regions") causes a build warning [1] on 6.1.y. That was due to
> > unnecessarily strict type check from max().
> >
> > 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 third one ("minmax: fix header
> > inclusions") are clean cherry-picks of upstream commit. For the third
> > one, a minor conflict fix was needed.
> >
> > [1] https://lore.kernel.org/2024071519-janitor-robe-779f@gregkh
>
> Thanks for these, I'll queue them up after this round of -rc releases go
> out in a few days.
All now queued up, MANY thanks for this, it fixed a different build
error that just got added to the 6.1 queue yesterday, as this problem
kept happening over and over due to backports breaking in different
ways.
greg k-h
prev parent reply other threads:[~2024-07-23 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 17:51 [PATCH 6.1.y 0/7] Backport patches for DAMON merge regions fix SeongJae Park
2024-07-16 17:51 ` [PATCH 6.1.y 1/7] minmax: sanity check constant bounds when clamping SeongJae Park
2024-07-16 17:52 ` [PATCH 6.1.y 2/7] minmax: clamp more efficiently by avoiding extra comparison SeongJae Park
2024-07-16 17:52 ` [PATCH 6.1.y 3/7] minmax: fix header inclusions SeongJae Park
2024-07-16 17:52 ` [PATCH 6.1.y 4/7] minmax: allow min()/max()/clamp() if the arguments have the same signedness SeongJae Park
2024-07-16 17:52 ` [PATCH 6.1.y 5/7] minmax: allow comparisons of 'int' against 'unsigned char/short' SeongJae Park
2024-07-16 17:52 ` [PATCH 6.1.y 6/7] minmax: relax check to allow comparison between unsigned arguments and signed constants SeongJae Park
2024-07-16 17:52 ` [PATCH 6.1.y 7/7] mm/damon/core: merge regions aggressively when max_nr_regions is unmet SeongJae Park
2024-07-23 12:09 ` Patch "mm/damon/core: merge regions aggressively when max_nr_regions is unmet" has been added to the 6.1-stable tree gregkh
2024-07-16 18:23 ` [PATCH 6.1.y 0/7] Backport patches for DAMON merge regions fix Greg KH
2024-07-23 12:10 ` Greg KH [this message]
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=2024072352-override-creasing-a0aa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.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.