From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman and "echo" output?
Date: Fri, 14 Dec 2018 07:23:43 -0500 [thread overview]
Message-ID: <20181214122343.GD8702@bill-the-cat> (raw)
In-Reply-To: <CAFOYHZDcieV+4zO2Oi3esYGgGU8vQ3o7cDLOS3UgZf6=o=vw=Q@mail.gmail.com>
On Fri, Dec 14, 2018 at 08:21:36PM +1300, Chris Packham wrote:
> Hi Tom, Simon,
>
> On Fri, Dec 14, 2018 at 5:01 AM Tom Rini <trini@konsulko.com> wrote:
> >
> > Hey Simon,
> >
> > How hard would it be to have buildman notice and print out the echo'd
> > warnings we have in the toplevel Makefile? By which I mean if you use
> > buildman to build omap3_beagle you see just the DT warnings but if you
> > run make by hand you also get:
> > ==================== WARNING ======================
> > This board does not use CONFIG_DM_MMC. Please update
> > the board to use CONFIG_DM_MMC before the v2019.04 release.
> > Failure to update by the deadline may result in board removal.
> > See doc/driver-model/MIGRATION.txt for more info.
> > ====================================================
> > ===================== WARNING ======================
> > This board does not use CONFIG_DM_USB. Please update
> > the board to use CONFIG_DM_USB before the v2019.07 release.
> > Failure to update by the deadline may result in board removal.
> > See doc/driver-model/MIGRATION.txt for more info.
> > ====================================================
> >
> > and as we want to get these things migrated we should make sure buildman
> > shows them I think. Thanks!
> >
>
> If these appear on stderr buildman seems to output them. I could turn
> the following into a proper patch if you want.
Seems like the most reasonable way to fix this, yes please, thanks!
--
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/20181214/2ae0756f/attachment.sig>
next prev parent reply other threads:[~2018-12-14 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 16:01 [U-Boot] buildman and "echo" output? Tom Rini
2018-12-14 7:21 ` Chris Packham
2018-12-14 12:23 ` Tom Rini [this message]
2018-12-14 17:23 ` Simon Glass
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=20181214122343.GD8702@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