From: "Michael S. Tsirkin" <mst@redhat.com>
To: Si-Wei Liu <si-wei.liu@oracle.com>
Cc: lvivier@redhat.com, virtualization@lists.linux-foundation.org,
eperezma@redhat.com, Eli Cohen <elic@nvidia.com>
Subject: Re: [PATCH 4/4] vdpa/mlx5: Fix tracking of current number of VQs
Date: Fri, 14 Jan 2022 15:25:33 -0500 [thread overview]
Message-ID: <20220114152443-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <8f1d7e2c-e8ca-4c09-f18c-72cd4c09c44f@oracle.com>
On Tue, Jan 11, 2022 at 02:14:47PM -0800, Si-Wei Liu wrote:
> Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>
Note: the correct format is:
Reviewed-by: Si-Wei Liu <si-wei.liu@oracle.com>
(with a space before <>).
Pls take care in the future.
Thanks!
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-01-14 20:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220111183400.38418-1-elic@nvidia.com>
[not found] ` <20220111183400.38418-2-elic@nvidia.com>
2022-01-11 21:46 ` [PATCH 1/4] vdpa: Avoid taking cf_mutex lock on get status Si-Wei Liu
2022-01-12 2:32 ` Jason Wang
[not found] ` <20220111183400.38418-4-elic@nvidia.com>
2022-01-11 21:47 ` [PATCH 3/4] vdpa/mlx5: Fix is_index_valid() to refer to features Si-Wei Liu
2022-01-12 2:35 ` Jason Wang
[not found] ` <20220111183400.38418-5-elic@nvidia.com>
2022-01-11 22:14 ` [PATCH 4/4] vdpa/mlx5: Fix tracking of current number of VQs Si-Wei Liu
2022-01-12 2:29 ` Jason Wang
2022-01-12 3:12 ` Si-Wei Liu
2022-01-12 3:57 ` Jason Wang
[not found] ` <20220112063732.GA196570@mtl-vdi-166.wap.labs.mlnx>
2022-01-12 7:46 ` Si-Wei Liu
2022-01-14 20:25 ` Michael S. Tsirkin [this message]
2022-01-12 2:35 ` Jason Wang
[not found] ` <20220111183400.38418-3-elic@nvidia.com>
2022-01-11 21:47 ` [PATCH 2/4] vdpa: Protect vdpa reset with cf_mutex Si-Wei Liu
2022-01-12 2:34 ` Jason Wang
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=20220114152443-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=elic@nvidia.com \
--cc=eperezma@redhat.com \
--cc=lvivier@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).