Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dmalloc: fix parallel builds
Date: Wed, 7 Jan 2015 14:17:46 +0100	[thread overview]
Message-ID: <20150107141746.274128f8@free-electrons.com> (raw)
In-Reply-To: <20150107130210.GA13534@vostro>

Dear Alex Suykov,

On Wed, 7 Jan 2015 15:02:10 +0200, Alex Suykov wrote:

> No, I don't use it myself. I was just looking through autobuild logs
> for unrelated reasons and kind of decided to fix what was clearly fixable.
> 
> Anyway, I'll send a version bump patch now, it looks like the changes
> are minor, and both Gentoo and OpenWRT have 5.5.2 already.

Good, thanks!

> I wonder if it makes sense to contact whoever sent that config
> to autobuild and ask for some feedback. Since dmalloc was enabled
> there, it was probably used for something.

The configs tested in the autobuilders are randomly generated:

 * A random architecture/toolchain configuration is selected amongst
   http://autobuild.buildroot.org/toolchains/configs/.

 * A random selection of packages is generated using
   "randpackageconfig".

So the configuration tested in the autobuilders are not submitted by
people, they are randomly generated by a script. That's how we test so
many combinations of packages/platforms.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-01-07 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03 11:05 [Buildroot] [PATCH] dmalloc: fix parallel builds Alex Suykov
2015-01-04 17:35 ` Thomas Petazzoni
2015-01-04 19:02   ` Alex Suykov
2015-01-04 20:41     ` Thomas Petazzoni
2015-01-07 13:02       ` Alex Suykov
2015-01-07 13:17         ` Thomas Petazzoni [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=20150107141746.274128f8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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