From: Yuanhe Shu <xiangzao@linux.alibaba.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yuanhe Shu <xiangzao@linux.alibaba.com>,
tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
xin@zytor.com, luto@kernel.org, jpoimboe@kernel.org,
peterz@infradead.org, rostedt@goodmis.org, rdunlap@infradead.org,
elver@google.com, andreyknvl@gmail.com, glider@google.com,
gor@linux.ibm.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] stacktrace: Provide arch_in_irqentry_text() hook
Date: Mon, 31 Aug 2026 17:06:18 +0800 [thread overview]
Message-ID: <20260831090623.2498707-1-xiangzao@linux.alibaba.com> (raw)
In-Reply-To: <20260827160615.c5cd19af1e4d9287d7870fb3@linux-foundation.org>
On Thu, Aug 27, 2026 at 04:06:15PM -0700, Andrew Morton wrote:
> Good call. I suggest that the same Fixes: be attached to this patch
> also, to help ensure that everything lands in the correct place.
Done in v2.
Thanks,
Yuanhe
next prev parent reply other threads:[~2026-08-31 9:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 15:00 [PATCH 0/2] x86/fred: Fix stack depot exhaustion on FRED systems Yuanhe Shu
2026-08-27 15:00 ` [PATCH 1/2] stacktrace: Provide arch_in_irqentry_text() hook Yuanhe Shu
2026-08-27 17:04 ` Bradley Morgan
2026-08-31 12:06 ` Yuanhe Shu
2026-08-31 12:09 ` Bradley Morgan
2026-08-27 23:06 ` Andrew Morton
2026-08-31 9:06 ` Yuanhe Shu [this message]
2026-08-27 15:00 ` [PATCH 2/2] x86/fred: Fix stack depot filtering of FRED event stacks Yuanhe Shu
2026-08-27 21:26 ` H. Peter Anvin
2026-08-31 11:29 ` Yuanhe Shu
2026-08-29 9:42 ` Peter Zijlstra
2026-08-31 8:59 ` Yuanhe Shu
2026-08-31 9:01 ` Peter Zijlstra
2026-08-31 11:25 ` Yuanhe Shu
2026-08-31 11:52 ` Peter Zijlstra
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=20260831090623.2498707-1-xiangzao@linux.alibaba.com \
--to=xiangzao@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gor@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=xin@zytor.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
all inboxes | Powered by JetHome®