From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org, linux@armlinux.org.uk,
bigeasy@linutronix.de, clrkwllms@kernel.org, rostedt@goodmis.org,
rmk+kernel@armlinux.org.uk, linusw@kernel.org,
kuninori.morimoto.gx@renesas.com, arnd@arndb.de,
xiqi2@huawei.com, ljs@kernel.org, wozizhi@huaweicloud.com
Cc: Sasha Levin <sashal@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
stable@vger.kernel.org, patches@lists.linux.dev,
lisongze2@huawei.com, wangbing6@huawei.com,
Xie Yuanbin <xieyuanbin1@huawei.com>
Subject: Re: [PATCH 5.10.y/5.15.y 4/4] ARM: 9484/1: enable interrupts when unhandled user faults are triggered
Date: Wed, 16 Sep 2026 15:28:20 -0400 [thread overview]
Message-ID: <daily-reply-20260916-0031-re-arm-9484-already-queued@kernel.org> (raw)
In-Reply-To: <20260916080011.170295-4-xieyuanbin1@huawei.com>
> [ Upstream commit e79ca91165d4fd18549c536abdb86101e889052f ]
This one is already queued for both 5.15 and 5.10, so please drop it from the
resend of the series.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-16 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 8:00 [PATCH 5.10.y/5.15.y 1/4] ARM: fix hash_name() fault Xie Yuanbin
2026-09-16 8:00 ` [PATCH 5.10.y/5.15.y 2/4] ARM: fix branch predictor hardening Xie Yuanbin
2026-09-16 8:00 ` [PATCH 5.10.y/5.15.y 3/4] ARM: ensure interrupts are enabled in __do_user_fault() Xie Yuanbin
2026-09-16 8:00 ` [PATCH 5.10.y/5.15.y 4/4] ARM: 9484/1: enable interrupts when unhandled user faults are triggered Xie Yuanbin
2026-09-16 19:28 ` Sasha Levin [this message]
2026-09-16 8:48 ` [PATCH 5.10.y/5.15.y 0/4] ARM: fix might_sleep() WARNING for mmap_write_lock() around show_pte() Xie Yuanbin
2026-09-16 19:27 ` [PATCH 5.10.y/5.15.y 1/4] ARM: fix hash_name() fault Sasha Levin
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=daily-reply-20260916-0031-re-arm-9484-already-queued@kernel.org \
--to=sashal@kernel.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux@armlinux.org.uk \
--cc=lisongze2@huawei.com \
--cc=ljs@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=wangbing6@huawei.com \
--cc=wozizhi@huaweicloud.com \
--cc=xieyuanbin1@huawei.com \
--cc=xiqi2@huawei.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