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] configs/imx6sabre: Create distinct pre-processed mkimage config files
Date: Fri, 23 Nov 2018 10:42:07 +0100	[thread overview]
Message-ID: <20181123104207.02996447@windsurf> (raw)
In-Reply-To: <1542912921-28407-1-git-send-email-festevam@gmail.com>

Hello,

On Thu, 22 Nov 2018 16:55:21 -0200, Fabio Estevam wrote:
> Commit 0c4bccf9e882 ("configs/imxsabre: Fix U-Boot parallel build issue")
> tried to fix the parallel build issue, but the real fix was developed
> later by Trent Piepho later, so add such commit to fix Buildroot
> build failures on rel_imx_4.9.x_1.0.0_ga NXP branch.
> 
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/123771053
> https://gitlab.com/buildroot.org/buildroot/-/jobs/123771054
> https://gitlab.com/buildroot.org/buildroot/-/jobs/123771055
> 
> Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
>  ...distinct-pre-processed-mkimage-config-fil.patch | 89 ++++++++++++++++++++++
>  ...emove-failure-when-no-IVT-offset-is-found.patch | 55 -------------
>  2 files changed, 89 insertions(+), 55 deletions(-)
>  create mode 100644 board/freescale/imx6sabre/patches/uboot/0002-imx-Create-distinct-pre-processed-mkimage-config-fil.patch
>  delete mode 100644 board/freescale/imx6sabre/patches/uboot/0002-imximage-Remove-failure-when-no-IVT-offset-is-found.patch

I tested, and it does fix the problem, so I've applied to master.
Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-11-23  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 18:55 [Buildroot] [PATCH] configs/imx6sabre: Create distinct pre-processed mkimage config files Fabio Estevam
2018-11-23  9:42 ` Thomas Petazzoni [this message]
2018-11-26 16:57 ` Peter Korsgaard

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=20181123104207.02996447@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