From: Juan Quintela <quintela@redhat.com>
To: Eduardo Otubo <eduardo.otubo@profitbricks.com>
Cc: pmoore@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] seccomp: libseccomp version varying according to arch
Date: Thu, 26 Mar 2015 17:21:11 +0100 [thread overview]
Message-ID: <871tkbwwzs.fsf@neno.neno> (raw)
In-Reply-To: <1427385385-30571-1-git-send-email-eduardo.otubo@profitbricks.com> (Eduardo Otubo's message of "Thu, 26 Mar 2015 16:56:25 +0100")
Eduardo Otubo <eduardo.otubo@profitbricks.com> wrote:
> Libseccomp dependency was mandating version 2.2.0 on all architectures
> and this was causing configure and virt-test to break on non-updates
> distros. This patch works-around it and give a more flexible way to
> check the version, giving more time for other distros to update
> libseccomp version.
>
> Signed-off-by: Eduardo Otubo <eduardo.otubo@profitbricks.com>
> Reported-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Tested-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2015-03-26 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 15:56 [Qemu-devel] [PATCH] seccomp: libseccomp version varying according to arch Eduardo Otubo
2015-03-26 16:21 ` Juan Quintela [this message]
2015-03-26 17:33 ` Peter Maydell
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=871tkbwwzs.fsf@neno.neno \
--to=quintela@redhat.com \
--cc=eduardo.otubo@profitbricks.com \
--cc=peter.maydell@linaro.org \
--cc=pmoore@redhat.com \
--cc=qemu-devel@nongnu.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).