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 v6 0/5] Support building barebox with an auxiliary config
Date: Sun, 24 Apr 2016 23:21:52 +0200	[thread overview]
Message-ID: <20160424232152.5e757542@free-electrons.com> (raw)
In-Reply-To: <cover.1461531859.git.pieter@boesman.nl>

Hello,

On Sun, 24 Apr 2016 23:15:22 +0200, Pieter Smith wrote:

> Revision history:
> v6: Review rework based on feedback from Thomas Pettazoni:
>     - Second config build renamed to auxiliary build.
>     - Primary package build moved to boot/barebox/barebox to keep things symmetric.
>     - Dropped already merged parts of series.

Thanks for this new version, looks good to me! I'll wait for Arnout to
comment and see if he has objections to this way of doing things.

Best regards,

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

  parent reply	other threads:[~2016-04-24 21:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 21:15 [Buildroot] [PATCH v6 0/5] Support building barebox with an auxiliary config Pieter Smith
2016-04-24 21:15 ` [Buildroot] [PATCH v6 1/3] barebox: prepare for auxiliarry build Pieter Smith
2016-05-01 12:34   ` Thomas Petazzoni
2016-05-01 20:49     ` Pieter Smith
2016-04-24 21:15 ` [Buildroot] [PATCH v6 2/3] barebox: support auxiliary config build Pieter Smith
2016-05-01 12:34   ` Thomas Petazzoni
2016-05-01 20:48     ` Pieter Smith
2016-04-24 21:15 ` [Buildroot] [PATCH v6 3/3] beaglebone: adds barebox bootloader defconfig Pieter Smith
2016-05-01 12:35   ` Thomas Petazzoni
2016-05-01 20:46     ` Pieter Smith
2016-04-24 21:21 ` Thomas Petazzoni [this message]
2016-04-24 21:24   ` [Buildroot] [PATCH v6 0/5] Support building barebox with an auxiliary config Pieter Smith

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=20160424232152.5e757542@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