From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, gregkh@linuxfoundation.org
Cc: Sasha Levin <sashal@kernel.org>, Xie Bo <xb@ultrarisc.com>,
Anup Patel <anup@brainfault.org>
Subject: Re: [PATCH 6.1.y] RISC-V: KVM: Serialize virtual interrupt pending state updates
Date: Wed, 29 Jul 2026 22:39:57 -0400 [thread overview]
Message-ID: <20260729223316.stable-0001@kernel.org> (raw)
In-Reply-To: <20260729013809.1745-1-xb@ultrarisc.com>
> [PATCH 6.1.y] RISC-V: KVM: Serialize virtual interrupt pending state updates
Queued for 6.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-30 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 6:52 FAILED: patch "[PATCH] RISC-V: KVM: Serialize virtual interrupt pending state" failed to apply to 6.1-stable tree gregkh
2026-07-29 1:38 ` [PATCH 6.1.y] RISC-V: KVM: Serialize virtual interrupt pending state updates Xie Bo
2026-07-30 2:39 ` Sasha Levin [this message]
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=20260729223316.stable-0001@kernel.org \
--to=sashal@kernel.org \
--cc=anup@brainfault.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=xb@ultrarisc.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