BACKPORT: seccomp: fix build warnings when there is no CONFIG_SECCOMP_FILTER
authorWill Drewry <wad@chromium.org>
Tue, 17 Apr 2012 19:48:58 +0000 (14:48 -0500)
committerGrant Grundler <grundler@google.com>
Thu, 24 May 2012 22:16:47 +0000 (15:16 -0700)
commit5071d5c144af87d0234ec871153591b1f1b76461
treea8feb5c8875072c1725b17d3071d119c32e827b5
parenta636b300a52d58ab4abc2cae9e7947278a384edd
BACKPORT: seccomp: fix build warnings when there is no CONFIG_SECCOMP_FILTER

If both audit and seccomp filter support are disabled, 'ret' is marked
as unused.

If just seccomp filter support is disabled, data and skip are considered
unused.

This change fixes those build warnings.

Change-Id: I2ec787dc6703cf5055e8e19b0800c2e80d0e73f4
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Will Drewry <wad@chromium.org>
Acked-by: Kees Cook <keescook@chromium.org>
Signed-off-by: James Morris <james.l.morris@oracle.com>
BUG=chromium-os:27878
TEST=none. Part of a much larger stack that really should merge together.

Change-Id: Id501094847dfb3bd67f1d3e91996939e495ab712
Reviewed-on: https://gerrit.chromium.org/gerrit/21373
Reviewed-by: Will Drewry <wad@chromium.org>
Tested-by: Will Drewry <wad@chromium.org>
kernel/seccomp.c