From: Eduardo Otubo <eduardo.otubo@profitbricks.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: qemu-devel@nongnu.org, Andrew Jones <drjones@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] configure: Enable seccomp sandbox for MIPS
Date: Tue, 12 Apr 2016 13:50:56 +0200 [thread overview]
Message-ID: <20160412115056.GA24071@vader> (raw)
In-Reply-To: <1460121394-31975-3-git-send-email-james.hogan@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Fri, Apr 08, 2016 at 02=16=34PM +0100, James Hogan wrote:
> Enable seccomp on MIPS since libseccomp version 2.2.0 when MIPS support
> was first added.
>
> Signed-off-by: James Hogan <james.hogan@imgtec.com>
> Reviewed-by: Andrew Jones <drjones@redhat.com>
> Cc: Eduardo Otubo <eduardo.otubo@profitbricks.com>
> Cc: Aurelien Jarno <aurelien@aurel32.net>
> ---
> configure | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/configure b/configure
> index 5db29f0245ae..f1c307bfc69c 100755
> --- a/configure
> +++ b/configure
> @@ -1872,6 +1872,9 @@ if test "$seccomp" != "no" ; then
> i386|x86_64)
> libseccomp_minver="2.1.0"
> ;;
> + mips)
> + libseccomp_minver="2.2.0"
> + ;;
> arm|aarch64)
> libseccomp_minver="2.2.3"
> ;;
> --
> 2.4.10
>
Acked-by: Eduardo Otubo <eduardo.otubo@profitbricks.com>
--
Eduardo Otubo
ProfitBricks GmbH
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-04-12 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 13:16 [Qemu-devel] [PATCH v2 0/2] Enable seccomp on MIPS James Hogan
2016-04-08 13:16 ` [Qemu-devel] [PATCH v2 1/2] seccomp: Whitelist cacheflush since 2.2.0 not 2.2.3 James Hogan
2016-04-12 11:52 ` Eduardo Otubo
2016-04-08 13:16 ` [Qemu-devel] [PATCH v2 2/2] configure: Enable seccomp sandbox for MIPS James Hogan
2016-04-12 11:50 ` Eduardo Otubo [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=20160412115056.GA24071@vader \
--to=eduardo.otubo@profitbricks.com \
--cc=aurelien@aurel32.net \
--cc=drjones@redhat.com \
--cc=james.hogan@imgtec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.