Linux Documentation
 help / color / mirror / Atom feed
From: "zhen.ni" <zhen.ni@easystack.cn>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	"Liam R . Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Brendan Jackman <brendan.jackman@linux.dev>,
	Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
	linux-mm@kvack.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] mm/page_owner: Add PID/TGID/COMM and cgroup filtering
Date: Tue, 1 Sep 2026 17:29:44 +0800	[thread overview]
Message-ID: <53e17480-31bd-4c90-aac3-6542b88ffb95@easystack.cn> (raw)
In-Reply-To: <apaG83-HCFTuASQ_@lucifer>



在 2026/9/1 16:10, Lorenzo Stoakes (ARM) 写道:
> Again you're failing to reply to kernel email in the usual style, and it's
> on you to figure out how to do that, not me.
> 
> Reply, inline, to what people have said to you.
> 

Understood - my previous mail was indeed a plan document rather than
inline replies.

Sorry for the noise.

> Do NOT ask them to read through your 'plan' document and give yet more of
> their time to compensate for you not following basic kernel procedure.
> 
> I have done hundreds (>1,000?) hrs of review upstream and I have only seen
> these kinds of 'summary - plan' emails since 2026.
> 

The timing has a simpler cause: Sashiko itself only started reviewing
patches in 2026.

I would normally prefer inline replies to review, but Sashiko did not
send any mail into this thread, so there is nothing to reply to
directly. Its findings are also heavily duplicated across patches, so
a grouped summary is the more appropriate form here.

> I am only asking you to engage upstream as everybody else does.
> 
> Since you ignored it, I ask you again - have you used an LLM here? If so
> follow kernel procedure as per the documentation I linked.

No. Every patch hunk and every fix/no-fix decision is my own.

> --
> Cheers, Lorenzo

Thanks,
Zhen

      reply	other threads:[~2026-09-01  9:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  3:13 [PATCH 0/8] mm/page_owner: Add PID/TGID/COMM and cgroup filtering Zhen Ni
2026-08-28  3:13 ` [PATCH 1/8] mm/page_owner: Add PID filtering support Zhen Ni
2026-08-28  3:13 ` [PATCH 2/8] mm/page_owner: Add TGID " Zhen Ni
2026-08-28  3:13 ` [PATCH 3/8] mm/page_owner: Add COMM filtering with wildcard support Zhen Ni
2026-08-28  3:13 ` [PATCH 4/8] mm/page_owner: Refactor memcg handling for cgroup filter support Zhen Ni
2026-08-28  3:13 ` [PATCH 5/8] mm/page_owner: Add memcg " Zhen Ni
2026-08-28  3:13 ` [PATCH 6/8] tools/mm: Add PID/TGID/COMM filtering support to page_owner_filter Zhen Ni
2026-08-28  3:13 ` [PATCH 7/8] tools/mm: Add memory cgroup " Zhen Ni
2026-08-28  3:13 ` [PATCH 8/8] Documentation: page_owner: Document PID/TGID/COMM and cgroup filters Zhen Ni
2026-08-28  7:03 ` [PATCH 0/8] mm/page_owner: Add PID/TGID/COMM and cgroup filtering Lorenzo Stoakes (ARM)
2026-08-28 18:36   ` Andrew Morton
2026-09-01  6:34     ` zhen.ni
2026-09-01  7:27       ` Lorenzo Stoakes (ARM)
2026-09-01  8:01         ` zhen.ni
2026-09-01  8:10           ` Lorenzo Stoakes (ARM)
2026-09-01  9:29             ` zhen.ni [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=53e17480-31bd-4c90-aac3-6542b88ffb95@easystack.cn \
    --to=zhen.ni@easystack.cn \
    --cc=akpm@linux-foundation.org \
    --cc=brendan.jackman@linux.dev \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=liam@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox