linux-kernel - Re: linux-next: build failure after merge of the final tree (devicetree tree related)

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: <CACxGe6ua4ev7-8Mvmvu4UKfGY12g0mTY-uAmRqcZnpFZnA_70w@mail.gmail.com>
Date:	Tue, 17 Apr 2012 16:39:16 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Thomas Abraham <thomas.abraham@...aro.org>
Subject: Re: linux-next: build failure after merge of the final tree
 (devicetree tree related)

On Mon, Apr 16, 2012 at 9:39 PM, Grant Likely <grant.likely@...retlab.ca> wrote:
> On Mon, Apr 16, 2012 at 9:23 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> Hi Grant,
>>
>> On Wed, 11 Apr 2012 18:35:34 -0600 Grant Likely <grant.likely@...retlab.ca> wrote:
>>>
>>> On Wed, Apr 11, 2012 at 6:31 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>> > Hi Grant,
>>> >
>>> > On Wed, 11 Apr 2012 15:11:55 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>> >>
>>> >> After merging the final tree, today's linux-next build (sparc64 defconfig)
>>> >> failed like this:
>>> >>
>>> >> drivers/of/of_mdio.c: In function 'of_mdiobus_register':
>>> >> drivers/of/of_mdio.c:75:4: error: implicit declaration of function 'irq_of_parse_and_map' [-Werror=implicit-function-declaration]
>>> >>
>>> >> Caused by commit e46c11b94787 ("of/irq: add empty irq_of_parse_and_map()
>>> >> for non-dt builds").  SPARC has CONFIG_OF but not CONFIG_OF_IRQ ...
>>> >>
>>> >> I have reverted that commit for today.
>>> >
>>> > That commit is actually in the devicetree-current tree.
>>>
>>> Yes, drop that tree or revert that commit.  There's nothing else in
>>> there and I didn't have time to pull it back today before you started
>>> linux-next for the day.  The change is bogus and I'll spin a proper
>>> fixup for tomorrow.
>>
>> Ping?
>
> Haven't got it done yet.  It's still safe to ignore that tree.

Should be fixed now.

g.
--
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/