From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v8 1/3] kernel: Move Device Tree support to kernel.bbclass
Date: Wed, 13 Sep 2017 09:24:54 +0100 [thread overview]
Message-ID: <1505291094.18640.30.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170912203608.14327-1-otavio@ossystems.com.br>
On Tue, 2017-09-12 at 17:36 -0300, Otavio Salvador wrote:
> The Device Tree is commonly used but it is still kept as a .inc file
> instead of a proper class. Instead now we move the Device Tree code
> to
> a kernel-devicetree class and automatically enable it when the
> KERNEL_DEVICETREE variable is set.
>
> To avoid breakage in existing layers, we kept a linux-dtb.inc file
> which raises a warning telling the user about the change so in next
> release this can be removed.
Still causing breakage:
https://autobuilder.yocto.io/builders/nightly-mips/builds/469/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-arm64/builds/454/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-mips-lsb/builds/464/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-mips64/builds/467/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-multilib/builds/489/steps/BuildImages_5/logs/stdio
https://autobuilder.yocto.io/builders/nightly-ppc/builds/488/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/477/steps/BuildImages/logs/stdio
All look like racing of do_compile_devicetree and do_make_scripts?
https://autobuilder.yocto.io/builders/nightly-arm/builds/537/steps/Buil
ding%20Toolchain%20Images/logs/stdio
"package kernel-devicetree-4.12.10+git0+42965d664f_fd16268214-r0.1.qemuarm does not have a compatible architecture"
Cheers,
Richard
next prev parent reply other threads:[~2017-09-13 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 20:36 [PATCH v8 1/3] kernel: Move Device Tree support to kernel.bbclass Otavio Salvador
2017-09-12 20:36 ` [PATCH v8 2/3] kernel-devicetree.bbclass: Rework to use tasks Otavio Salvador
2017-09-12 20:36 ` [PATCH v8 3/3] kernel-devicetree.bbclass: Add support to generate append to kernel Otavio Salvador
2017-09-13 8:15 ` André Draszik
2017-09-13 12:30 ` Otavio Salvador
2017-09-14 10:26 ` André Draszik
2017-09-14 12:13 ` Otavio Salvador
2017-09-15 7:55 ` André Draszik
2017-09-14 10:19 ` André Draszik
2017-09-13 8:24 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-12 13:45 [PATCH v8 1/3] kernel: Move Device Tree support to kernel.bbclass Otavio Salvador
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=1505291094.18640.30.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.