From: Paolo Bonzini <pbonzini@redhat.com>
To: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Cc: samuel.thibault@ens-lyon.org, j@getutm.app
Subject: Re: [PATCH 0/5] Update libslirp & make it a subproject
Date: Thu, 14 Jan 2021 14:33:34 +0100 [thread overview]
Message-ID: <04472318-3dfe-d2d3-9852-51b5e7269f46@redhat.com> (raw)
In-Reply-To: <20210114125605.1227742-1-marcandre.lureau@redhat.com>
On 14/01/21 13:56, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Hi,
>
> Here is a few patches to update libslirp to git upstream.
> Since it now supports meson subproject(), adapt the build
> system to use it, and related fixes.
>
> Marc-André Lureau (5):
> build-sys: remove unused LIBS
> build-sys: set global arguments for cflags/ldflags
> build-sys: add libvhost-user missing dependencies
> slirp: update to git master
> build-sys: make libslirp a meson subproject
>
> configure | 34 +-----------
> meson.build | 78 +++++----------------------
> .gitmodules | 6 +--
> slirp | 1 -
> subprojects/libslirp | 1 +
> subprojects/libvhost-user/meson.build | 3 ++
> 6 files changed, 20 insertions(+), 103 deletions(-)
> delete mode 160000 slirp
> create mode 160000 subprojects/libslirp
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
prev parent reply other threads:[~2021-01-14 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 12:56 [PATCH 0/5] Update libslirp & make it a subproject marcandre.lureau
2021-01-14 12:56 ` [PATCH 1/5] build-sys: remove unused LIBS marcandre.lureau
2021-01-14 12:56 ` [PATCH 2/5] build-sys: set global arguments for cflags/ldflags marcandre.lureau
2021-01-14 12:56 ` [PATCH 3/5] build-sys: add libvhost-user missing dependencies marcandre.lureau
2021-01-14 13:17 ` Philippe Mathieu-Daudé
2021-01-14 12:56 ` [PATCH 4/5] slirp: update to git master marcandre.lureau
2021-01-14 12:56 ` [PATCH 5/5] build-sys: make libslirp a meson subproject marcandre.lureau
2021-01-14 13:33 ` Paolo Bonzini [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=04472318-3dfe-d2d3-9852-51b5e7269f46@redhat.com \
--to=pbonzini@redhat.com \
--cc=j@getutm.app \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).