From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: alok.a.tiwari@oracle.com, linux-kernel@vger.kernel.org,
darren.kenny@oracle.com, david@redhat.com, mst@redhat.com,
jasowang@redhat.com, eperezma@redhat.com,
virtualization@lists.linux.dev
Subject: Re: [PATCH v2 1/3] virtio: Fix typo in register_virtio_device() doc comment
Date: Fri, 13 Jun 2025 09:45:53 +0800 [thread overview]
Message-ID: <1749779153.2349436-2-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <20250529084350.3145699-1-alok.a.tiwari@oracle.com>
On Thu, 29 May 2025 01:42:39 -0700, Alok Tiwari <alok.a.tiwari@oracle.com> wrote:
> Corrected "suceess" to "success" in the function documentation
> for clarity.
>
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
> Acked-by: Jason Wang <jasowang@redhat.com>
Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> ---
> v1 -> v2
> No changes; only added Acked-by: Jason Wang.
> ---
> drivers/virtio/virtio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/virtio/virtio.c b/drivers/virtio/virtio.c
> index 95d5d7993e5b..2c022640ec4b 100644
> --- a/drivers/virtio/virtio.c
> +++ b/drivers/virtio/virtio.c
> @@ -506,7 +506,7 @@ static int virtio_device_of_init(struct virtio_device *dev)
> * On error, the caller must call put_device on &@dev->dev (and not kfree),
> * as another code path may have obtained a reference to @dev.
> *
> - * Returns: 0 on suceess, -error on failure
> + * Returns: 0 on success, -error on failure
> */
> int register_virtio_device(struct virtio_device *dev)
> {
> --
> 2.47.1
>
prev parent reply other threads:[~2025-06-13 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 8:42 Alok Tiwari
2025-05-29 8:42 ` [PATCH v2 2/3] virtio-mem: fix multiple typos in struct comments and function docs Alok Tiwari
2025-05-30 9:30 ` David Hildenbrand
2025-05-29 8:42 ` [PATCH v2 3/3] virtio_ring: Fix typos in comments and documentation Alok Tiwari
2025-06-13 1:45 ` Xuan Zhuo [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=1749779153.2349436-2-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=alok.a.tiwari@oracle.com \
--cc=darren.kenny@oracle.com \
--cc=david@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux.dev \
/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
all inboxes | Powered by JetHome®