From: Karl Mehltretter <kmehltretter@gmail.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Ashish Kalra <ashish.kalra@amd.com>,
linux-coco@lists.linux.dev, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Brijesh Singh <brijesh.singh@amd.com>
Subject: [PATCH] Documentation: virt: Fix the struct snp_guest_request_ioctl name in sev-guest.rst
Date: Sat, 5 Sep 2026 11:29:42 +0200 [thread overview]
Message-ID: <20260905092942.41558-1-kmehltretter@gmail.com> (raw)
struct snp_user_guest_request does not exist; the name is struct
snp_guest_request_ioctl.
Use the real name.
Fixes: fce96cf04430 ("virt: Add SEV-SNP guest driver")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
Documentation/virt/coco/sev-guest.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/coco/sev-guest.rst b/Documentation/virt/coco/sev-guest.rst
index 93debceb6eb0..3371ebc29e8b 100644
--- a/Documentation/virt/coco/sev-guest.rst
+++ b/Documentation/virt/coco/sev-guest.rst
@@ -38,7 +38,7 @@ along with a description:
are not detailed, but errors with specific meanings are.
The guest ioctl should be issued on a file descriptor of the /dev/sev-guest
-device. The ioctl accepts struct snp_user_guest_request. The input and
+device. The ioctl accepts struct snp_guest_request_ioctl. The input and
output structure is specified through the req_data and resp_data field
respectively. If the ioctl fails to execute due to a firmware error, then
the fw_error code will be set, otherwise fw_error will be set to -1.
--
2.53.0
next reply other threads:[~2026-09-05 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 9:29 Karl Mehltretter [this message]
2026-09-05 17:20 ` [PATCH] Documentation: virt: Fix the struct snp_guest_request_ioctl name in sev-guest.rst Randy Dunlap
2026-09-09 14:51 ` Tom Lendacky
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=20260905092942.41558-1-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=ashish.kalra@amd.com \
--cc=brijesh.singh@amd.com \
--cc=corbet@lwn.net \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=thomas.lendacky@amd.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).