From: Randy Dunlap <rdunlap@infradead.org>
To: Mark Brown <broonie@kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 9th (of: unittest: testcases)
Date: Tue, 10 Oct 2017 10:33:22 -0700 [thread overview]
Message-ID: <7524d1e5-137c-cb78-c24f-6a9701e46701@infradead.org> (raw)
In-Reply-To: <20171009212122.wx4lgnecmqyzuywq@sirena.co.uk>
On 10/09/17 14:21, Mark Brown wrote:
> For my birthday I've gone and got myself a linux-next tree:
>
> Changes since 20170929:
>
> The net-next and drm trees lost their build failures but the rcu tree
> gained one.
I don't know what this is but it's new AFAIK.
(seen on i386 and x86_64)
DTC drivers/of/unittest-data/testcases.dtb
drivers/of/unittest-data/testcases.dtb: Warning (interrupts_extended_property): Could not get phandle node for /__local_fixups__/testcase-data/interrupts/interrupts-extended0:interrupts-extended(cell 3)
drivers/of/unittest-data/testcases.dtb: Warning (interrupts_property): interrupts size is (4), expected multiple of 8 in /testcase-data/testcase-device2
--
~Randy
next parent reply other threads:[~2017-10-10 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171009212122.wx4lgnecmqyzuywq@sirena.co.uk>
2017-10-10 17:33 ` Randy Dunlap [this message]
[not found] ` <7524d1e5-137c-cb78-c24f-6a9701e46701-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-10-10 18:26 ` linux-next: Tree for Oct 9th (of: unittest: testcases) Rob Herring
2017-10-10 18:34 ` Randy Dunlap
2017-10-11 18:11 ` Frank Rowand
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=7524d1e5-137c-cb78-c24f-6a9701e46701@infradead.org \
--to=rdunlap@infradead.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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).