From: Randy Dunlap <rdunlap@infradead.org>
To: Xuewen Wang <wangxuewen@kylinos.cn>,
hughd@google.com, baolin.wang@linux.alibaba.com,
rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, corbet@lwn.net,
skhan@linuxfoundation.org, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] mm/shmem: trace swapin results and order fallbacks
Date: Tue, 27 Oct 2026 16:55:01 -0700 [thread overview]
Message-ID: <f34f14ca-21bf-4ae4-9e7b-da7f72d1b134@infradead.org> (raw)
In-Reply-To: <20261027094014.2432692-2-wangxuewen@kylinos.cn>
On 10/27/26 2:40 AM, Xuewen Wang wrote:
> diff --git a/Documentation/trace/events-shmem.rst b/Documentation/trace/events-shmem.rst
> new file mode 100644
> index 000000000000..45da82761360
> --- /dev/null
> +++ b/Documentation/trace/events-shmem.rst
> @@ -0,0 +1,73 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +Tmpfs and shmem events
> +=====================
Underline is one character too short:
Documentation/trace/events-shmem.rst:4: WARNING: Title underline too short.
Tmpfs and shmem events
===================== [docutils]
--
~Randy
next prev parent reply other threads:[~2026-10-27 23:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 9:40 [PATCH 0/2] mm/shmem: trace swapin results and allocation fallbacks Xuewen Wang
2026-10-27 9:40 ` [PATCH 1/2] mm/shmem: trace swapin results and order fallbacks Xuewen Wang
2026-10-27 23:55 ` Randy Dunlap [this message]
2026-10-28 3:27 ` wangxuewen
2026-10-27 9:40 ` [PATCH 2/2] mm/shmem: trace folio allocation failures and fallbacks Xuewen Wang
2026-10-28 7:56 ` [PATCH 0/2] mm/shmem: trace swapin results and allocation fallbacks Baolin Wang
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=f34f14ca-21bf-4ae4-9e7b-da7f72d1b134@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=hughd@google.com \
--cc=linux-doc@vger.kernel.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 \
--cc=skhan@linuxfoundation.org \
--cc=wangxuewen@kylinos.cn \
/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
all inboxes | Powered by JetHome®