Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 10:14:16 +0000	[thread overview]
Message-ID: <5641C378.8020506@imgtec.com> (raw)
In-Reply-To: <20151110110041.56a13980@free-electrons.com>

On 11/10/2015 10:00 AM, Thomas Petazzoni wrote:
> Markos,
> 
> On Tue, 10 Nov 2015 09:49:45 +0000, Markos Chandras wrote:
> 
>> ping?
> 
> I think the reason I still don't apply this patch is because I'm not
> happy with Buildroot doing all this complicated logic to install the
> tests, and that it should be part of the libseccomp build system to
> provide a mechanism to do that easily.
> 
> So if you want to see this integrated, I would recommend to work with
> upstream libseccomp to implement something allowing the installation of
> tests, and then use it in Buildroot.

Hi Thomas,

Ok fair enough

-- 
markos

      reply	other threads:[~2015-11-10 10:14 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
2015-11-10 10:00             ` Thomas Petazzoni
2015-11-10 10:14               ` Markos Chandras [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=5641C378.8020506@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox