From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932504AbdJJSeY (ORCPT ); Tue, 10 Oct 2017 14:34:24 -0400 Received: from merlin.infradead.org ([205.233.59.134]:56630 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932294AbdJJSeW (ORCPT ); Tue, 10 Oct 2017 14:34:22 -0400 Subject: Re: linux-next: Tree for Oct 9th (of: unittest: testcases) To: Rob Herring , Frank Rowand Cc: Mark Brown , Linux-Next Mailing List , Linux Kernel Mailing List , "devicetree@vger.kernel.org" References: <20171009212122.wx4lgnecmqyzuywq@sirena.co.uk> <7524d1e5-137c-cb78-c24f-6a9701e46701@infradead.org> From: Randy Dunlap Message-ID: Date: Tue, 10 Oct 2017 11:34:20 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/10/17 11:26, Rob Herring wrote: > +Frank > > On Tue, Oct 10, 2017 at 12:33 PM, Randy Dunlap wrote: >> 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) > > Yes, new dtc version with new warnings. > >> 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) > > Frank, this is in __local_fixups__, we should be able to remove that > now as the necessary dtc changes are in place, right? > >> drivers/of/unittest-data/testcases.dtb: Warning (interrupts_property): interrupts size is (4), expected multiple of 8 in /testcase-data/testcase-device2 > > This one is purposely bad data to feed the unit test. If I suppress > it, then it is suppressed everywhere in the unit test data. Thanks for the info. -- ~Randy