Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ltp-testsuite: add --with-open-posix-testsuite
Date: Thu, 3 May 2018 21:55:04 +0200	[thread overview]
Message-ID: <20180503215504.356b46be@windsurf> (raw)
In-Reply-To: <CAFXrp_cbD89wmzAf44aNjHfQS+ixvMUqMmxFxeLjLbvGDr3FFA@mail.gmail.com>

Hello Ciro,

On Thu, 3 May 2018 17:03:16 +0100, Ciro Santilli wrote:
> The issues mentioned on the removed comments were resolved,
> tested in QEMU x86_64 and aarch64.
> 
> Signed-off-by: Ciro Santilli <ciro.santilli@gmail.com>
> ---
> This patch supposes that the removed comments imply that a default
> --with-open-posix-testsuite
> is desirable (and I confirm that it does not take unreasoble build
> time or disk space),
> and that there is no generic way to add autotools configs to packages:
> https://stackoverflow.com/questions/44341188/how-to-pass-extra-custom-configure-autotools-options-to-a-buildroot-package

Thanks for this contribution. However, your patch was corrupted, so it
would be nice to use "git send-email" next time to submit a patch.

However, since the patch was simple, I fixed it up, and applied. Thanks
again!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-05-03 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 16:03 [Buildroot] [PATCH] ltp-testsuite: add --with-open-posix-testsuite Ciro Santilli
     [not found] ` <CAFXrp_fe0s-a8F4Zh5h2gP5_krm_6vdqbd1E0MKL-3q8ENfJ6A@mail.gmail.com>
2018-05-03 17:21   ` Petr Vorel
2018-05-03 19:55 ` Thomas Petazzoni [this message]
2018-05-03 20:01   ` Ciro Santilli
2018-05-03 20:49 ` Arnout Vandecappelle

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=20180503215504.356b46be@windsurf \
    --to=thomas.petazzoni@bootlin.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