From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: zhenwei pi <pizhenwei@bytedance.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, marcandre.lureau@redhat.com,
berrange@redhat.com, thuth@redhat.com
Subject: Re: [PATCH v2 1/1] meson: Remove libibumad dependence
Date: Tue, 11 Jun 2024 11:49:31 +0200 [thread overview]
Message-ID: <100d2b67-18ef-44a0-abe3-c9cd0fa0d392@linaro.org> (raw)
In-Reply-To: <20240611092743.59255-2-pizhenwei@bytedance.com>
On 11/6/24 11:27, zhenwei pi wrote:
> RDMA based migration has no dependence on libumad. libibverbs and
> librdmacm are enough.
> libumad was used by rdmacm-mux which has been already removed. It's
> remained mistakenly.
>
> Fixes: 1dfd42c4264b ("hw/rdma: Remove deprecated pvrdma device and rdmacm-mux helper")
> Cc: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> meson.build | 4 +---
> tests/lcitool/projects/qemu.yml | 1 -
> 2 files changed, 1 insertion(+), 4 deletions(-)
> diff --git a/tests/lcitool/projects/qemu.yml b/tests/lcitool/projects/qemu.yml
> index 070d7f4706..0c85784259 100644
> --- a/tests/lcitool/projects/qemu.yml
> +++ b/tests/lcitool/projects/qemu.yml
> @@ -47,7 +47,6 @@ packages:
> - libfdt
> - libffi
> - libgcrypt
> - - libibumad
> - libibverbs
> - libiscsi
> - libjemalloc
You didn't run "make lcitool-refresh", see:
https://www.qemu.org/docs/master/devel/testing#adding-new-build-pre-requisites
prev parent reply other threads:[~2024-06-11 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 9:27 [PATCH v2 0/1] meson: Remove libibumad dependence zhenwei pi
2024-06-11 9:27 ` [PATCH v2 1/1] " zhenwei pi
2024-06-11 9:49 ` Philippe Mathieu-Daudé [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=100d2b67-18ef-44a0-abe3-c9cd0fa0d392@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).