From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Nhat Pham <nphamcs@gmail.com>
Cc: Xueyuan Chen <xueyuan.chen21@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] mm: remove CONFIG_ZSMALLOC_STAT
Date: Wed, 11 Nov 2026 13:38:20 +0900 [thread overview]
Message-ID: <avPxIH-JtqVvTzBF@google.com> (raw)
In-Reply-To: <CAKEwX=PNpMr5x4gTo_OK5D5EgKPDvZx2e2=95-4_SV8zq37VnQ@mail.gmail.com>
On (26/11/10 08:03), Nhat Pham wrote:
> On Mon, Nov 9, 2026 at 5:59 AM Xueyuan Chen <xueyuan.chen21@gmail.com> wrote:
> >
> > The statistics interface now uses the debugfs API stubs directly, so
> > CONFIG_ZSMALLOC_STAT no longer controls any zsmalloc code.
> >
> > Remove the Kconfig entry. Replace the remaining CONFIG_ZSMALLOC_STAT
> > settings with CONFIG_DEBUG_FS=y.
> >
> > Suggested-by: Nhat Pham <nphamcs@gmail.com>
> > Signed-off-by: Xueyuan Chen <xueyuan.chen21@gmail.com>
>
> I wonder if we can just squash all 3 patches lol
I agree. Let's have just one patch.
next prev parent reply other threads:[~2026-11-11 4:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 12:59 [PATCH v2 0/3] mm/zsmalloc: remove CONFIG_ZSMALLOC_STAT Xueyuan Chen
2026-11-09 12:59 ` [PATCH v2 1/3] " Xueyuan Chen
2026-11-10 15:00 ` Nhat Pham
2026-11-11 4:35 ` Sergey Senozhatsky
2026-11-11 11:29 ` Xueyuan Chen
2026-11-11 11:21 ` Xueyuan Chen
2026-11-09 12:59 ` [PATCH v2 2/3] mm: " Xueyuan Chen
2026-11-10 15:03 ` Nhat Pham
2026-11-11 4:38 ` Sergey Senozhatsky [this message]
2026-11-11 11:31 ` Xueyuan Chen
2026-11-11 4:33 ` Sergey Senozhatsky
2026-11-11 4:37 ` Sergey Senozhatsky
2026-11-09 12:59 ` [PATCH v2 3/3] docs: zsmalloc: describe statistics with CONFIG_DEBUG_FS Xueyuan Chen
2026-11-10 15:03 ` Nhat Pham
2026-11-11 11:40 ` Xueyuan Chen
2026-11-11 6:25 ` Sergey Senozhatsky
2026-11-11 11:50 ` Xueyuan Chen
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=avPxIH-JtqVvTzBF@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=xueyuan.chen21@gmail.com \
/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.