From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Minchan Kim <minchan@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Kconfig: fixup zsmalloc configuration
Date: Tue, 3 Sep 2024 13:43:47 +0900 [thread overview]
Message-ID: <20240903044347.GE9738@google.com> (raw)
In-Reply-To: <20240903040143.1580705-1-senozhatsky@chromium.org>
On (24/09/03 13:00), Sergey Senozhatsky wrote:
>
> Fixes: Fixes: aa3ba6d72ce0 ...
>
Developers, developers
next prev parent reply other threads:[~2024-09-03 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 4:00 [PATCH] mm: Kconfig: fixup zsmalloc configuration Sergey Senozhatsky
2024-09-03 4:43 ` Sergey Senozhatsky [this message]
2024-09-03 17:55 ` Johannes Weiner
2024-09-03 21:28 ` Andrew Morton
2024-09-04 3:12 ` Sergey Senozhatsky
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=20240903044347.GE9738@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@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;
as well as URLs for NNTP newsgroup(s).