From: Alex Williamson <alex@shazbot.org>
To: Joseph Salisbury <joseph.salisbury@oracle.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, alex@shazbot.org
Subject: Re: [PATCH] vfio: uapi: fix comment typo
Date: Fri, 20 Mar 2026 15:17:48 -0600 [thread overview]
Message-ID: <20260320151748.299fd9ce@shazbot.org> (raw)
In-Reply-To: <20260316185617.166414-1-joseph.salisbury@oracle.com>
On Mon, 16 Mar 2026 14:56:17 -0400
Joseph Salisbury <joseph.salisbury@oracle.com> wrote:
> The file contains a spelling error in a source comment (succes).
>
> Typos in comments reduce readability and make text searches less reliable
> for developers and maintainers.
>
> Replace 'succes' with 'success' in the affected comment. This is a
> comment-only cleanup and does not change behavior.
>
> Fixes: 607ca46e97a1 ("UAPI: (Scripted) Disintegrate include/linux")
> Cc: stable@vger.kernel.org
> Signed-off-by: Joseph Salisbury <joseph.salisbury@oracle.com>
> ---
> include/uapi/linux/vfio.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> index bb7b89330d35..63d56c1fbf6f 100644
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -141,7 +141,7 @@ struct vfio_info_cap_header {
> *
> * Retrieve information about the group. Fills in provided
> * struct vfio_group_info. Caller sets argsz.
> - * Return: 0 on succes, -errno on failure.
> + * Return: 0 on success, -errno on failure.
> * Availability: Always
> */
> struct vfio_group_status {
Applied to vfio next branch for v7.1. Fixes and stable tags dropped.
Thanks,
Alex
prev parent reply other threads:[~2026-03-20 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 18:56 [PATCH] vfio: uapi: fix comment typo Joseph Salisbury
2026-03-16 23:49 ` [External] : " Joseph Salisbury
2026-03-20 21:17 ` Alex Williamson [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=20260320151748.299fd9ce@shazbot.org \
--to=alex@shazbot.org \
--cc=joseph.salisbury@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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