From: Miaohe Lin <linmiaohe@huawei.com>
To: Xie Yuanbin <xieyuanbin1@huawei.com>
Cc: <linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-trace-kernel@vger.kernel.org>,
<torvalds@linux-foundation.org>, <lilinjie8@huawei.com>,
<liaohua4@huawei.com>, <david@kernel.org>, <qiuxu.zhuo@intel.com>,
<bp@alien8.de>, <akpm@linux-foundation.org>,
<rostedt@goodmis.org>, <nao.horiguchi@gmail.com>,
<mhiramat@kernel.org>, <mchehab+huawei@kernel.org>,
<tony.luck@intel.com>, <yi1.lai@intel.com>
Subject: Re: [PATCH] mm/memory-failure: trace: change memory_failure_event to ras subsystem
Date: Mon, 8 Jun 2026 19:27:33 +0800 [thread overview]
Message-ID: <5d7eb2a0-e9ed-da53-fbde-548901b55141@huawei.com> (raw)
In-Reply-To: <20260605081213.154660-1-xieyuanbin1@huawei.com>
On 2026/6/5 16:12, Xie Yuanbin wrote:
> For historical version, commit 97f0b1345219 ("tracing: add trace event
> for memory-failure") introduced memory_failure_event in ras subsystem.
> commit 31807483d395 ("mm/memory-failure: remove the selection of RAS")
> changed memory_failure_event to memory_failure subsystem. This breaks
> the backward compatibility, some user programs rely on it.
>
> Change memory_failure_event to ras subsystem to keep backward
> compatibility.
>
> Fixes: 31807483d395 ("mm/memory-failure: remove the selection of RAS")
With David's comment addressed:
Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks.
.
next prev parent reply other threads:[~2026-06-08 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 8:12 [PATCH] mm/memory-failure: trace: change memory_failure_event to ras subsystem Xie Yuanbin
2026-06-05 8:51 ` David Hildenbrand (Arm)
2026-06-05 13:09 ` Zhuo, Qiuxu
2026-06-08 11:27 ` Miaohe Lin [this message]
2026-06-08 12:14 ` Lance Yang
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=5d7eb2a0-e9ed-da53-fbde-548901b55141@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=david@kernel.org \
--cc=liaohua4@huawei.com \
--cc=lilinjie8@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mhiramat@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=qiuxu.zhuo@intel.com \
--cc=rostedt@goodmis.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=xieyuanbin1@huawei.com \
--cc=yi1.lai@intel.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