Linux Trace Kernel
 help / color / mirror / Atom feed
From: Meijing Zhao <zhaomeijing100@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-trace-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/3] mm: trace: decode architecture-specific VMA flags
Date: Fri,  7 Aug 2026 11:13:49 +0800	[thread overview]
Message-ID: <20260807031349.3119855-1-zhaomeijing100@gmail.com> (raw)
In-Reply-To: <20260723092905.761037-1-zhaomeijing100@gmail.com>

Hi,

A gentle ping on this patch series. It has been about two weeks since
it was posted, and I have not received any feedback yet.

Would you have a chance to take a look? Please let me know if I should
rebase or resend the series.

For reference, the original thread is available here:
https://lore.kernel.org/linux-mm/20260723092905.761037-1-zhaomeijing100@gmail.com/

Thanks,
Meijing Zhao

  parent reply	other threads:[~2026-08-07  3:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  9:29 [PATCH RESEND 0/3] mm: trace: decode architecture-specific VMA flags Meijing Zhao
2026-07-23  9:29 ` [PATCH RESEND 1/3] mm: trace: decode arm64 and sparc64 VM_ARCH_1 flags Meijing Zhao
2026-07-23  9:29 ` [PATCH RESEND 2/3] mm: trace: decode MTE and shadow stack VMA flags Meijing Zhao
2026-07-23  9:29 ` [PATCH RESEND 3/3] mm: trace: name protection key encoding bits Meijing Zhao
2026-08-07  3:13 ` Meijing Zhao [this message]
2026-08-07 12:47   ` [PATCH RESEND 0/3] mm: trace: decode architecture-specific VMA flags Steven Rostedt
2026-08-07 19:50     ` Andrew Morton
2026-08-07 20:26       ` Steven Rostedt

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=20260807031349.3119855-1-zhaomeijing100@gmail.com \
    --to=zhaomeijing100@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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