From: Hanna Czenczek <hreitz@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>,
berto@igalia.com, kwolf@redhat.com, groug@kaod.org,
qemu_oss@crudebyte.com
Cc: arei.gonglei@huawei.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org, berrange@redhat.com
Subject: Re: [PATCH v3 2/6] test-throttle: use enum ThrottleType
Date: Fri, 21 Jul 2023 17:43:19 +0200 [thread overview]
Message-ID: <caaddc1c-1bbb-6c40-5be1-b10831ee84a5@redhat.com> (raw)
In-Reply-To: <20230713064111.558652-3-pizhenwei@bytedance.com>
On 13.07.23 08:41, zhenwei pi wrote:
> Use enum ThrottleType instead in the throttle test codes.
>
> Reviewed-by: Alberto Garcia <berto@igalia.com>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> tests/unit/test-throttle.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Hanna Czenczek <hreitz@redhat.com>
next prev parent reply other threads:[~2023-07-21 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 6:41 [PATCH v3 0/6] Misc fixes for throttle zhenwei pi
2023-07-13 6:41 ` [PATCH v3 1/6] throttle: introduce enum ThrottleType zhenwei pi
2023-07-21 15:42 ` Hanna Czenczek
2023-07-13 6:41 ` [PATCH v3 2/6] test-throttle: use " zhenwei pi
2023-07-21 15:43 ` Hanna Czenczek [this message]
2023-07-13 6:41 ` [PATCH v3 3/6] throttle: support read-only and write-only zhenwei pi
2023-07-21 15:42 ` Hanna Czenczek
2023-07-13 6:41 ` [PATCH v3 4/6] test-throttle: test read only and write only zhenwei pi
2023-07-21 15:43 ` Hanna Czenczek
2023-07-13 6:41 ` [PATCH v3 5/6] cryptodev: use NULL throttle timer cb for read direction zhenwei pi
2023-07-21 15:42 ` Hanna Czenczek
2023-07-13 6:41 ` [PATCH v3 6/6] throttle: use enum ThrottleType instead of bool is_write zhenwei pi
2023-07-21 16:03 ` Hanna Czenczek
2023-07-21 1:28 ` PING: [PATCH v3 0/6] Misc fixes for throttle zhenwei pi
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=caaddc1c-1bbb-6c40-5be1-b10831ee84a5@redhat.com \
--to=hreitz@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=berto@igalia.com \
--cc=groug@kaod.org \
--cc=kwolf@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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).