From: Nam Cao <namcao@linutronix.de>
To: Rui Qi <qirui.001@bytedance.com>,
palmer@dabbelt.com, pjw@kernel.org, aou@eecs.berkeley.edu,
alex@ghiti.fr, conor@kernel.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
samuel.holland@sifive.com, Rui Qi <qirui.001@bytedance.com>
Subject: Re: [PATCH] riscv: Fix 32-bit call_on_irq_stack() frame pointer ABI
Date: Wed, 24 Jun 2026 14:38:17 +0200 [thread overview]
Message-ID: <87o6h06rly.fsf@yellow.woof> (raw)
In-Reply-To: <20260624113148.3723541-1-qirui.001@bytedance.com>
"Rui Qi" <qirui.001@bytedance.com> writes:
> This is a resubmission of Samuel Holland's patch [1] which was
> posted in May 2024 but never merged. The bug still exists in the
> current tree.
>
> [1] https://lore.kernel.org/all/20240530001733.1407654-2-samuel.holland@sifive.com/
I don't think we should keep this part in the commit message. And
Matthew's Reviewed-by should be included.
But I leave that to the maintainers, the diff looks correct to me.
Reviewed-by: Nam Cao <namcao@linutronix.de>
Nam
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: Rui Qi <qirui.001@bytedance.com>,
palmer@dabbelt.com, pjw@kernel.org, aou@eecs.berkeley.edu,
alex@ghiti.fr, conor@kernel.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
samuel.holland@sifive.com, Rui Qi <qirui.001@bytedance.com>
Subject: Re: [PATCH] riscv: Fix 32-bit call_on_irq_stack() frame pointer ABI
Date: Wed, 24 Jun 2026 14:38:17 +0200 [thread overview]
Message-ID: <87o6h06rly.fsf@yellow.woof> (raw)
In-Reply-To: <20260624113148.3723541-1-qirui.001@bytedance.com>
"Rui Qi" <qirui.001@bytedance.com> writes:
> This is a resubmission of Samuel Holland's patch [1] which was
> posted in May 2024 but never merged. The bug still exists in the
> current tree.
>
> [1] https://lore.kernel.org/all/20240530001733.1407654-2-samuel.holland@sifive.com/
I don't think we should keep this part in the commit message. And
Matthew's Reviewed-by should be included.
But I leave that to the maintainers, the diff looks correct to me.
Reviewed-by: Nam Cao <namcao@linutronix.de>
Nam
next prev parent reply other threads:[~2026-06-24 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 11:31 [PATCH] riscv: Fix 32-bit call_on_irq_stack() frame pointer ABI Rui Qi
2026-06-24 11:31 ` Rui Qi
2026-06-24 12:38 ` Nam Cao [this message]
2026-06-24 12:38 ` Nam Cao
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=87o6h06rly.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=qirui.001@bytedance.com \
--cc=samuel.holland@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.