From: Alexander Potapenko <glider@google.com>
To: itazur@amazon.com
Cc: Dave.Martin@arm.com, corbet@lwn.net, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
marc.zyngier@arm.com, pbonzini@redhat.com, zulinx86@gmail.com
Subject: Re: [PATCH v2] docs: KVM: Fix register ID of SPSR_FIQ
Date: Fri, 2 Aug 2024 15:20:36 +0200 [thread overview]
Message-ID: <20240802132036.914457-1-glider@google.com> (raw)
In-Reply-To: <20230606154628.95498-1-itazur@amazon.com>
Hi folks,
I also came across this inconsistency in the docs. What happened to the patch in question?
next prev parent reply other threads:[~2024-08-02 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 15:46 [PATCH v2] docs: KVM: Fix register ID of SPSR_FIQ Takahiro Itazuri
2024-08-02 13:20 ` Alexander Potapenko [this message]
2024-08-04 8:17 ` Zenghui Yu
2024-08-04 9:21 ` Marc Zyngier
2024-08-05 22:13 ` Oliver Upton
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=20240802132036.914457-1-glider@google.com \
--to=glider@google.com \
--cc=Dave.Martin@arm.com \
--cc=corbet@lwn.net \
--cc=itazur@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=zulinx86@gmail.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;
as well as URLs for NNTP newsgroup(s).