From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Minchan Kim <minchan@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] zsmalloc: minor documentation updates
Date: Sun, 26 Mar 2023 10:21:23 +0900 [thread overview]
Message-ID: <20230326012123.GB3269998@google.com> (raw)
In-Reply-To: <20230325125419.1b86c2331d94f86bad30d2aa@linux-foundation.org>
On (23/03/25 12:54), Andrew Morton wrote:
> 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?
Sure.
For zsmalloc-document-new-fullness-grouping.patch it's not very trivial,
since the patch covers several internal zsmalloc changes: new fullness
grouping and new zsmalloc classes stats fullness format. I think it's OK
to just say that it fixes patch that converted zsmalloc classes stats to
new format.
prev parent reply other threads:[~2023-03-26 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 2:46 [PATCH 0/2] zsmalloc: minor documentation updates 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 ` [PATCH 0/2] zsmalloc: minor documentation updates Andrew Morton
2023-03-26 1:21 ` Sergey Senozhatsky [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=20230326012123.GB3269998@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 \
/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.