From: Scott Garman <scott.a.garman@intel.com>
To: Leon Woestenberg <sidebranch.openembedded@gmail.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
Yocto Project <yocto@yoctoproject.org>,
"Purdie, Richard" <richard.purdie@intel.com>
Subject: Re: [denzil-next BREAKAGE] Silent breakage in denzil-next --- uImage*.dts no longer generated
Date: Wed, 01 Aug 2012 09:56:47 -0700 [thread overview]
Message-ID: <50195FCF.1030004@intel.com> (raw)
In-Reply-To: <CAMvUbCyh0LPs-s9ShTG7UexGC_f0s16_6WfFhbhGbNsxpjvRaw@mail.gmail.com>
On 08/01/2012 07:50 AM, Leon Woestenberg wrote:
> Hello Scott, all,
>
> On Wed, Aug 1, 2012 at 4:31 PM, Leon Woestenberg
> <sidebranch.openembedded@gmail.com
> <mailto:sidebranch.openembedded@gmail.com>> wrote:
>
> Hello Scott,
>
> I tested your denzil-next branch but found breakage that will not
> fail the (auto) build.
>
> I'm hitting the "Warning: ${DTS_FILE} is not available!" case.
>
> Disregard the breakage. Local user error; my KERNEL_DEVICETREE missed
> the "${S}" prefix.
>
> However, that being said, should we silently fail with a warning of the
> specified device tree (DTS) is missing? This is clearly a change of
> behaviour that makes the build prone to user errors, as I just demonstrated.
>
> I rather have the build fail.
Hi Leon,
Thanks for bringing this up. I believe Matthew made the original request
for this commit (linux-dtb: add multi-dtb build support,
a40d795ee97d8ada6a0b76c9741a8653fd646893). I'm cc:'ing him on this email
as well as Richard Purdie, who has yet to review the new commits in my
denzil-next branch and may also have some input on this issue.
The question in my mind right now is whether this change is too
risky/change-inducing for a point-release.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-08-01 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 14:31 [denzil-next BREAKAGE] Silent breakage in denzil-next --- uImage*.dts no longer generated Leon Woestenberg
2012-08-01 14:50 ` Leon Woestenberg
2012-08-01 16:56 ` Scott Garman [this message]
2012-08-01 18:05 ` McClintock Matthew-B29882
2012-08-02 10:41 ` Leon Woestenberg
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=50195FCF.1030004@intel.com \
--to=scott.a.garman@intel.com \
--cc=B29882@freescale.com \
--cc=richard.purdie@intel.com \
--cc=sidebranch.openembedded@gmail.com \
--cc=yocto@yoctoproject.org \
/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.