From: Andrew Morton <akpm@linux-foundation.org>
To: "Kanchana P. Sridhar" <kanchanapsridhar2026@gmail.com>
Cc: Yosry Ahmed <yosry@kernel.org>,
hannes@cmpxchg.org, nphamcs@gmail.com, chengming.zhou@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
herbert@gondor.apana.org.au, senozhatsky@chromium.org
Subject: Re: [PATCH v3 0/2] zswap pool per-CPU acomp_ctx simplifications
Date: Tue, 31 Mar 2026 15:19:50 -0700 [thread overview]
Message-ID: <20260331151950.54771bdaf8ddfac766abe3c4@linux-foundation.org> (raw)
In-Reply-To: <CACpmpofnKdfprZG=WHW-jOeeXGF47MYoCJDbkZJnemQU+x4wdw@mail.gmail.com>
On Tue, 31 Mar 2026 13:58:37 -0700 "Kanchana P. Sridhar" <kanchanapsridhar2026@gmail.com> wrote:
> > > Kanchana P. Sridhar (2):
> > > mm: zswap: Remove redundant checks in zswap_cpu_comp_dead().
> > > mm: zswap: Tie per-CPU acomp_ctx lifetime to the pool.
> >
> > Sashiko was able to apply the patches and doesn't seem to find any
> > regressions: https://sashiko.dev/#/patchset/20260331183351.29844-1-kanchanapsridhar2026%40gmail.com.
>
> That's good to know, thanks for confirming Yosry!
Thanks, both.
I'm surprised that a patchset of this signficance got through AI review
without comment, actually.
I've confirmed that the code changes in v3 are identical to those in
v2, which I removed a couple of days ago for Sashiko's benefit. v2 was
added to mm.git March 16. So all good, I've re-added this series.
next prev parent reply other threads:[~2026-03-31 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 18:33 Kanchana P. Sridhar
2026-03-31 18:33 ` [PATCH v3 1/2] mm: zswap: Remove redundant checks in zswap_cpu_comp_dead() Kanchana P. Sridhar
2026-03-31 18:33 ` [PATCH v3 2/2] mm: zswap: Tie per-CPU acomp_ctx lifetime to the pool Kanchana P. Sridhar
2026-03-31 19:22 ` [PATCH v3 0/2] zswap pool per-CPU acomp_ctx simplifications Yosry Ahmed
2026-03-31 20:58 ` Kanchana P. Sridhar
2026-03-31 22:19 ` Andrew Morton [this message]
2026-03-31 22:38 ` Kanchana P. Sridhar
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=20260331151950.54771bdaf8ddfac766abe3c4@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=herbert@gondor.apana.org.au \
--cc=kanchanapsridhar2026@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=yosry@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox