From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/8] travis-ci: Do not make buildman warnings fatal
Date: Fri, 21 Oct 2016 07:19:00 -0400 [thread overview]
Message-ID: <20161021111900.GT18591@bill-the-cat> (raw)
In-Reply-To: <5809C630.8030202@denx.de>
On Fri, Oct 21, 2016 at 09:39:28AM +0200, Heiko Schocher wrote:
> Hello Tom,
>
> Am 20.10.2016 um 21:26 schrieb Tom Rini:
> >We currently will always see a number of warnings due to device tree
> >issues. These (and other warnings) should not make the build be marked
> >as failure so catch exit status 129 specifically and return 0 in that
> >case.
> >
> >Cc: Heiko Schocher <hs@denx.de>
> >Signed-off-by: Tom Rini <trini@konsulko.com>
>
> You mean here this "Warning (unit_address_vs_reg):" warnings?
And a few others as well, depending on toolchain.
> IIRC I posted some month ago a patch, which suppress them ... the
> patch was rejected, with the plausible reason, that we should fix
> this issues ... so I started and posted some dts fix patches, also
> rejected with the reason that this should come from linux syncs ...
>
> Hmm.. do we syncs for our DTS files with linux?
Yes. I suppose that for example for x86/sandbox we should take your
patches. But yes, for other platforms where we are not the
authoritative source the fixes need to be pushed to Linux first and
merged in. Some platforms sync more often with upstream than others in
this regard.
> Nevertheless: we should at least fix this for travis, so:
>
> Reviewed-by: Heiko Schocher <hs@denx.de>
Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161021/d7b90dc0/attachment.sig>
next prev parent reply other threads:[~2016-10-21 11:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 19:25 [U-Boot] [PATCH 0/8] Various travis-ci improvements Tom Rini
2016-10-20 19:25 ` [U-Boot] [PATCH 1/8] test/py: ensure a log section exists for skipped tests Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 2/8] travis-ci: Switch to Ubuntu 14.04 'Trusty Tahr' Tom Rini
2016-10-21 7:27 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 3/8] travis-ci: Use a git URI for dtc.git Tom Rini
2016-10-21 7:32 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 4/8] travis-ci: Do not make buildman warnings fatal Tom Rini
2016-10-21 7:39 ` Heiko Schocher
2016-10-21 11:19 ` Tom Rini [this message]
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 5/8] travis-ci: Update toolchain and buildman usage Tom Rini
2016-10-21 7:40 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 6/8] travis-ci: Add more architectures Tom Rini
2016-10-21 7:41 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 7/8] travis-ci: Drop 'TEST_CMD' Tom Rini
2016-10-21 7:54 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 8/8] travis-ci: Add test.py for various qemu platforms Tom Rini
2016-10-20 19:40 ` [U-Boot] [PATCH v2 " Tom Rini
2016-10-21 18:24 ` Stephen Warren
2016-10-22 12:56 ` Tom Rini
2016-10-24 22:21 ` Stephen Warren
2016-10-24 22:46 ` Tom Rini
2016-10-24 15:23 ` Tom Rini
2016-10-21 9:22 ` [U-Boot] [PATCH " Heiko Schocher
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=20161021111900.GT18591@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