From: Cornelia Huck <cohuck@redhat.com>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: wanghaibin.wang@huawei.com, alex.williamson@redhat.com,
kwankhede@nvidia.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] vfio: Fix vfio_listener_log_sync function name typo
Date: Fri, 18 Dec 2020 16:50:42 +0100 [thread overview]
Message-ID: <20201218165042.59b972c9.cohuck@redhat.com> (raw)
In-Reply-To: <20201204014240.772-1-yuzenghui@huawei.com>
On Fri, 4 Dec 2020 09:42:40 +0800
Zenghui Yu <yuzenghui@huawei.com> wrote:
> There is an obvious typo in the function name of the .log_sync() callback.
> Spell it correctly.
>
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
> ---
> hw/vfio/common.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2020-12-18 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 1:42 [PATCH] vfio: Fix vfio_listener_log_sync function name typo Zenghui Yu
2020-12-18 15:50 ` Cornelia Huck [this message]
2021-03-02 22:11 ` Alex Williamson
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=20201218165042.59b972c9.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.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).