From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] libseccomp: Add new config option to build and install tests
Date: Tue, 10 Nov 2015 09:49:45 +0000 [thread overview]
Message-ID: <5641BDB9.1000601@imgtec.com> (raw)
In-Reply-To: <560E3F24.90109@imgtec.com>
On 10/02/2015 09:24 AM, Markos Chandras wrote:
> On 09/21/2015 10:28 AM, Markos Chandras wrote:
>> Add new config option to allow building and installing the libseccomp
>> testsuite on the target. It's useful for testing the kernels'
>> seccomp behavior for the target architecture.
>>
>> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
>> ---
>> changes since v2:
>> - Move installation path for tests to /usr/share/libseccomp
>> - Do not install python files. We don't support python + libseccomp
>> at the moment so there is no point in installing these tests yet.
>>
>> changes since v1:
>> - Drop compile hook for tests and use MAKE_OPTS instead
>> ---
>
> ping?
>
ping?
--
markos
next prev parent reply other threads:[~2015-11-10 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 13:53 [Buildroot] [PATCH] libseccomp: Add new config option to build and install tests Markos Chandras
2015-09-17 17:02 ` Vicente Olivert Riera
2015-09-18 8:19 ` [Buildroot] [PATCH v2] " Markos Chandras
2015-09-18 8:36 ` Vicente Olivert Riera
2015-09-18 8:39 ` Vicente Olivert Riera
2015-09-20 12:46 ` Thomas Petazzoni
2015-09-21 8:39 ` Markos Chandras
2015-09-21 9:28 ` [Buildroot] [PATCH v3] " Markos Chandras
2015-09-21 10:40 ` Vicente Olivert Riera
2015-10-02 8:24 ` Markos Chandras
2015-11-10 9:49 ` Markos Chandras [this message]
2015-11-10 10:00 ` Thomas Petazzoni
2015-11-10 10:14 ` Markos Chandras
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=5641BDB9.1000601@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=buildroot@busybox.net \
/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.