From: Markus Armbruster <armbru@redhat.com>
To: Xie Yongji <xieyongji@bytedance.com>
Cc: kwolf@redhat.com, stefanha@redhat.com, armbru@redhat.com,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/4] libvduse: Fix the incorrect function name
Date: Wed, 29 Jun 2022 11:37:31 +0200 [thread overview]
Message-ID: <87fsjnq084.fsf@pond.sub.org> (raw)
In-Reply-To: <20220627090203.87-2-xieyongji@bytedance.com> (Xie Yongji's message of "Mon, 27 Jun 2022 17:02:00 +0800")
Xie Yongji <xieyongji@bytedance.com> writes:
> In vduse_name_is_valid(), we actually check whether
> the name is invalid or not. So let's change the
> function name to vduse_name_is_invalid() to match
> the behavior.
>
> Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2022-06-29 9:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 9:01 [PATCH 0/4] Fix some coverity issues on VDUSE Xie Yongji
2022-06-27 9:02 ` [PATCH 1/4] libvduse: Fix the incorrect function name Xie Yongji
2022-06-29 9:37 ` Markus Armbruster [this message]
2022-06-27 9:02 ` [PATCH 2/4] libvduse: Replace strcpy() with strncpy() Xie Yongji
2022-06-28 0:25 ` Richard Henderson
2022-06-28 2:59 ` Yongji Xie
2022-06-29 9:38 ` Markus Armbruster
2022-06-27 9:02 ` [PATCH 3/4] libvduse: Pass positive value to strerror() Xie Yongji
2022-06-28 0:26 ` Richard Henderson
2022-06-29 9:38 ` Markus Armbruster
2022-06-27 9:02 ` [PATCH 4/4] libvduse: Check the return value of some ioctls Xie Yongji
2022-06-29 9:41 ` Markus Armbruster
2022-06-29 11:10 ` Yongji Xie
2022-06-29 11:39 ` Markus Armbruster
2022-06-29 12:37 ` Yongji Xie
2022-06-29 13:22 ` Markus Armbruster
2022-06-29 13:28 ` Yongji Xie
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=87fsjnq084.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xieyongji@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.