From: Oscar Salvador <osalvador@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
Waiman Long <longman@redhat.com>,
Suren Baghdasaryan <surenb@google.com>,
Marco Elver <elver@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Alexander Potapenko <glider@google.com>
Subject: Re: [PATCH v5 0/3] page_owner: print stacks and their counter
Date: Wed, 17 May 2023 05:27:22 +0200 [thread overview]
Message-ID: <d2c5f359b0212a94390a97b04b874356@suse.de> (raw)
In-Reply-To: <20230516141245.356200756ff3750ef4f12094@linux-foundation.org>
On 2023-05-16 23:12, Andrew Morton wrote:
> Documentation/mm/page_owner.rst is feeling very sad.
I will definitely update the docs, sorry about that.
> I'll toss it in there for some testing for now. The changelogs would
> benefit from a bit of proofreading, please - quite a few typos and
> grammaros.
Let me fix those.
Thanks Andrew
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2023-05-17 3:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 18:25 Oscar Salvador
2023-05-16 18:25 ` [PATCH v5 1/3] lib/stackdepot: Add a refcount field in stack_record Oscar Salvador
2023-05-16 18:25 ` [PATCH v5 2/3] mm, page_owner: Add page_owner_stacks file to print out only stacks and their counte Oscar Salvador
2023-05-17 0:59 ` kernel test robot
2023-05-22 8:27 ` Alexander Potapenko
2023-05-16 18:25 ` [PATCH v5 3/3] mm,page_owner: Filter out stacks by a threshold counter Oscar Salvador
2023-05-22 8:40 ` Alexander Potapenko
2023-06-12 10:53 ` Vlastimil Babka
2023-05-16 21:12 ` [PATCH v5 0/3] page_owner: print stacks and their counter Andrew Morton
2023-05-17 3:27 ` Oscar Salvador [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-16 14:03 Oscar Salvador
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=d2c5f359b0212a94390a97b04b874356@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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
Powered by JetHome