qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Helge Deller <deller@gmx.de>
Cc: qemu-devel@nongnu.org, Thomas Huth <thuth@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] configure: Relax check for libseccomp
Date: Fri, 5 Apr 2019 08:34:06 +0100	[thread overview]
Message-ID: <20190405073406.GB6105@redhat.com> (raw)
In-Reply-To: <20190404183923.GA22347@ls3530.dellerweb.de>

On Thu, Apr 04, 2019 at 08:39:23PM +0200, Helge Deller wrote:
> All major distributions do support libseccomp version >= 2.3.0, so there
> is no need to special-case on various architectures any longer.
> 
> Signed-off-by: Helge Deller <deller@gmx.de>

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Helge Deller <deller@gmx.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] configure: Relax check for libseccomp
Date: Fri, 5 Apr 2019 08:34:06 +0100	[thread overview]
Message-ID: <20190405073406.GB6105@redhat.com> (raw)
Message-ID: <20190405073406.E5aMN0jhjhPJHW-G0ovO25i0LWJrbJSOcrwAcrl8tpM@z> (raw)
In-Reply-To: <20190404183923.GA22347@ls3530.dellerweb.de>

On Thu, Apr 04, 2019 at 08:39:23PM +0200, Helge Deller wrote:
> All major distributions do support libseccomp version >= 2.3.0, so there
> is no need to special-case on various architectures any longer.
> 
> Signed-off-by: Helge Deller <deller@gmx.de>

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|


  parent reply	other threads:[~2019-04-05  7:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 12:49 [Qemu-devel] [PATCH] configure: Relax check for libseccomp Helge Deller
2019-04-03 15:16 ` Peter Maydell
2019-04-03 15:17   ` Peter Maydell
2019-04-03 15:55   ` Helge Deller
2019-04-03 21:04   ` Eduardo Habkost
2019-04-04  1:44     ` Peter Maydell
2019-04-03 16:17 ` Daniel P. Berrangé
2019-04-04  1:53   ` Peter Maydell
2019-04-04  6:59     ` Thomas Huth
2019-04-04  8:56       ` Daniel P. Berrangé
2019-04-04 18:39         ` [Qemu-devel] [PATCH v2] " Helge Deller
2019-04-04 20:01           ` Thomas Huth
2019-04-05  9:01             ` Eduardo Otubo
2019-04-05  9:01               ` Eduardo Otubo
2019-04-05  7:34           ` Daniel P. Berrangé [this message]
2019-04-05  7:34             ` Daniel P. Berrangé
2019-04-05  8:50           ` Philippe Mathieu-Daudé
2019-04-05  8:50             ` Philippe Mathieu-Daudé

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=20190405073406.GB6105@redhat.com \
    --to=berrange@redhat.com \
    --cc=deller@gmx.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).