From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra: Indicate that binman makes all three output files
Date: Thu, 26 Jul 2018 15:39:41 -0400 [thread overview]
Message-ID: <20180726193941.GB7590@bill-the-cat> (raw)
In-Reply-To: <8494fc65-ac24-b857-80d6-3869cccf8eac@wwwdotorg.org>
On Thu, Jul 26, 2018 at 01:37:31PM -0600, Stephen Warren wrote:
> On 07/23/2018 09:27 AM, Stephen Warren wrote:
> >On 07/20/2018 07:49 PM, Simon Glass wrote:
> >>Use GNU make pattern rules to indicate that a single run of binman
> >>produces all three Tegra output files. The avoids make running binman
> >>three times (perhaps in parallel) and those instances inteferring with
> >>each other.
> >>
> >>See http://patchwork.ozlabs.org/patch/944611/ for the bug report.
> >
> >Tested-by: Stephen Warren <swarren@nvidia.com>
> >
> >(This make feature is very odd; specifying n targets without a % means
> >they're separate rules, but specifying n targets with a % means it's a
> >single rule that generates n targets. Nice inconsistency on make's part!)
>
> Any chance we can apply this ASAP to the main u-boot.git master branch?
> Pretty much all my Jenkins builds are failing some random subset of boards
> because of this issue. Thanks.
If Tom W is fine, I'm happy to pick it up directly.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180726/8c15b615/attachment.sig>
next prev parent reply other threads:[~2018-07-26 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 1:49 [U-Boot] [PATCH] tegra: Indicate that binman makes all three output files Simon Glass
2018-07-23 15:27 ` Stephen Warren
2018-07-26 19:37 ` Stephen Warren
2018-07-26 19:39 ` Tom Rini [this message]
2018-07-26 19:45 ` Tom Warren
2018-07-26 19:38 ` Simon Glass
2018-07-26 19:55 ` [U-Boot] " Tom Rini
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=20180726193941.GB7590@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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;
as well as URLs for NNTP newsgroup(s).