linux-kernel - Re: linux-next: build failure after merge of the battery tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151008120424.6813920f@canb.auug.org.au>
Date:	Thu, 8 Oct 2015 12:04:24 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Sebastian Reichel <sre@...nel.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Marek Belisko <marek@...delico.com>
Subject: Re: linux-next: build failure after merge of the battery tree

Hi Sebastian,

On Fri, 2 Oct 2015 11:49:32 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Tue, 29 Sep 2015 11:45:31 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > After merging the battery tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > ERROR (phandle_references): Reference to non-existent node or label "twl4030_madc"
> > ERROR: Input tree has errors, aborting (use -f to force output)
> > scripts/Makefile.lib:293: recipe for target 'arch/arm/boot/dts/omap3-beagle-xm-ab.dtb' failed
> > 
> > and many more ...
> > 
> > Caused by commit
> > 
> >   af19161aaed7 ("ARM: dts: twl4030: Add iio properties for bci subnode")
> > 
> > Presumably some updates to other files were missed.
> > 
> > I have used the battery tree from next-20150925 fot today.
> 
> I am still getting this error.

Ping?

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/