From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Minchan Kim <minchan@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] zsmalloc: minor documentation updates
Date: Sat, 25 Mar 2023 12:54:19 -0700 [thread overview]
Message-ID: <20230325125419.1b86c2331d94f86bad30d2aa@linux-foundation.org> (raw)
In-Reply-To: <20230325024631.2817153-1-senozhatsky@chromium.org>
On Sat, 25 Mar 2023 11:46:29 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> Two minor patches that bring zsmalloc documentation up to date.
>
It would be best to keep the in-kernel documentation accurate
for the kernel version with which it is shipped. So can you
please suggest a Fixes: for these two?
next prev parent reply other threads:[~2023-03-25 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 2:46 Sergey Senozhatsky
2023-03-25 2:46 ` [PATCH 1/2] zsmalloc: document new fullness grouping Sergey Senozhatsky
2023-03-25 2:46 ` [PATCH 2/2] zsmalloc: document freeable stats Sergey Senozhatsky
2023-03-25 19:54 ` Andrew Morton [this message]
2023-03-26 1:21 ` [PATCH 0/2] zsmalloc: minor documentation updates 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=20230325125419.1b86c2331d94f86bad30d2aa@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=senozhatsky@chromium.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