Re: [PATCH] samples/seccomp: Add standalone config option

On Wed, Jul 6, 2016 at 2:53 AM, Olof Johansson wrote: > Add a separate Kconfig option for SAMPLES_SECCOMP. > > Main reason for this is that, just like other samples, it's forced to be a > module. > > Without this, since the sample is a target only controlled by > CONFIG_SECCOMP_FILTER, the sample

Re: [PATCH] samples/seccomp: Add standalone config option

Hi, On Wed, Jul 6, 2016 at 10:55 AM, Kees Cook wrote: > On Wed, Jul 6, 2016 at 2:53 AM, Olof Johansson wrote: >> Add a separate Kconfig option for SAMPLES_SECCOMP. >> >> Main reason for this is that, just like other samples, it's forced to be a >> module. >> >> Without this, since the sample is

Re: [PATCH] samples/seccomp: Add standalone config option

On Wed, Jul 6, 2016 at 2:53 AM, Olof Johansson wrote: > Add a separate Kconfig option for SAMPLES_SECCOMP. > > Main reason for this is that, just like other samples, it's forced to be a > module. > > Without this, since the sample is a target only controlled by > CONFIG_SECCOMP_FILTER, the sample

[PATCH] samples/seccomp: Add standalone config option

Add a separate Kconfig option for SAMPLES_SECCOMP. Main reason for this is that, just like other samples, it's forced to be a module. Without this, since the sample is a target only controlled by CONFIG_SECCOMP_FILTER, the samples will be built before include files are put in place properly. For