All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/7] configs: fix build of calao_qil_a9260_defconfig
Date: Sun, 04 Oct 2015 19:06:31 +0200	[thread overview]
Message-ID: <87pp0uk1go.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1443901457-7914-7-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sat, 3 Oct 2015 20:44:16 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > The Barebox, AT91Bootstrap and Linux patches for the Calao QIL A9260
 > board are all located in the same directory, board/calao/qil-a9260/,
 > with only a prefix to indicate to which component they apply.

 > Unfortunately, since commit 0eba4759fab9d093afacac77a0ac31f1f0b3cceb
 > ("packages: apply custom patches using *.patch instead of
 > <pkg>-*.patch"), the logic to apply custom patches in Barebox and
 > AT91Bootstrap has been changed from applying <package>-*.patch to
 > applying *.patch (in order to be consistent with what we do for all
 > packages in Buildroot).

 > However, this had the effect of trying to apply both the AT91Bootstrap
 > and Barebox patches on both packages, which obviously cannot work.

 > This commit fixes that by moving patches around, and switching to use
 > BR2_GLOBAL_PATCH_DIR for all of Barebox, AT91Bootstrap and Linux
 > patches.

 > In addition, the defconfig was not specifying explicitly which Barebox
 > version to use, so right now it's trying to use Barebox 2015.09, on
 > which the board-specific patch does not apply. So we've forced to use
 > Barebox 2012.08, which was the lastest release available at the time
 > the defconfig was initially contributed.

 > Cc: Gregory Hermant <gregory.hermant@calao-systems.com>
 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2015-10-04 17:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03 19:44 [Buildroot] [PATCH 0/7] configs: fix build of many defconfigs Thomas Petazzoni
2015-10-03 19:44 ` [Buildroot] [PATCH 1/7] configs: remove gnublin_defconfig Thomas Petazzoni
2015-10-03 21:06   ` Peter Seiderer
2015-10-04  8:15     ` Thomas Petazzoni
2015-10-04 17:01   ` Peter Korsgaard
2015-10-03 19:44 ` [Buildroot] [PATCH 2/7] dtc: add host build Thomas Petazzoni
2015-10-03 21:13   ` Peter Seiderer
2015-10-04 18:12     ` Peter Korsgaard
2015-10-04 18:14   ` Peter Korsgaard
2015-10-03 19:44 ` [Buildroot] [PATCH 3/7] u-boot: add an option to indicate that DTC is needed Thomas Petazzoni
2015-10-03 21:19   ` Arnout Vandecappelle
2015-10-04 18:15   ` Peter Korsgaard
2015-10-03 19:44 ` [Buildroot] [PATCH 4/7] configs: fix configurations that need host-dtc Thomas Petazzoni
2015-10-04 18:16   ` Peter Korsgaard
2015-10-03 19:44 ` [Buildroot] [PATCH 5/7] configs: fix build of calao_usb_a9g20_lpw_defconfig Thomas Petazzoni
2015-10-04 17:06   ` Peter Korsgaard
2015-10-03 19:44 ` [Buildroot] [PATCH 6/7] configs: fix build of calao_qil_a9260_defconfig Thomas Petazzoni
2015-10-04 17:06   ` Peter Korsgaard [this message]
2015-10-03 19:44 ` [Buildroot] [PATCH 7/7] configs: remove old/broken Atmel configurations Thomas Petazzoni
2015-10-03 20:41   ` Alexandre Belloni
2015-10-03 20:54     ` Arnout Vandecappelle
2015-10-13 21:30   ` Thomas Petazzoni

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=87pp0uk1go.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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.