All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/dtc: backport upstream fix solving Assertion Error with some .dts files
Date: Mon, 26 Nov 2018 17:26:47 +0100	[thread overview]
Message-ID: <87bm6bx0s8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181124090403.4045-2-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Sat, 24 Nov 2018 10:04:03 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > The build of U-Boot on Microchip (formerly Atmel) platforms currently
 > fails to build with an Assertion Error in dtc. This happens since we
 > bumped dtc from 1.4.4 to 1.4.7, as a regression was introduced in dtc
 > 1.4.6, and fixed post-1.4.7. This commit backports the upstream commit
 > to resolve this Assertion Error.

 > The build error was:

 > dtc: livetree.c:438: propval_cell: Assertion `prop->val.len == sizeof(cell_t)' failed.
 > dtc: livetree.c:438: propval_cell: Assertion `prop->val.len == sizeof(cell_t)' failed.
 > Aborted (core dumped)

 > Fixes:

 >   https://gitlab.com/buildroot.org/buildroot/-/jobs/124434438
 >   (and numerous other similar build failures)

 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-11-26 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24  9:04 [Buildroot] [PATCH 1/2] package/dtc: renumber patches correctly Thomas Petazzoni
2018-11-24  9:04 ` [Buildroot] [PATCH 2/2] package/dtc: backport upstream fix solving Assertion Error with some .dts files Thomas Petazzoni
2018-11-26 16:26   ` Peter Korsgaard [this message]
2018-11-26 18:04   ` Peter Korsgaard
2018-11-26 16:26 ` [Buildroot] [PATCH 1/2] package/dtc: renumber patches correctly Peter Korsgaard
2018-11-26 18:03 ` 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=87bm6bx0s8.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.