linux-kernel - Re: linux-next: build failure after merge of the gpio 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: <CACRpkdaXd7nJYpix_nztF6iuSuKYb9H4FMgRr9NcxFRp+vEyzw@mail.gmail.com>
Date:	Tue, 22 Dec 2015 10:08:58 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Robert Jarzmik <robert.jarzmik@...e.fr>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the gpio tree

On Tue, Dec 22, 2015 at 7:57 AM, Robert Jarzmik <robert.jarzmik@...e.fr> wrote:
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
>
>> Hi Linus,
>>
>> After merging the gpio tree, today's linux-next build (lots without
>> CONFIG_OF) failed like this:
>>
>> drivers/gpio/gpio-pxa.c: In function 'pxa_gpio_probe':
>> drivers/gpio/gpio-pxa.c:648:12: error: 'pxa_irq_domain_ops' undeclared (first use in this function)
>>
>> Caused by commit
>>
>>   384ca3c6a28d ("gpio: pxa: change the interrupt management")
>>
>> The reference to pxa_irq_domain_ops was moved out of the protection of
>> CONFIG_OF ...
>>
>> Discovered after the release.
>
> Hi Stephen,
>
> The fix has been sent in http://www.spinics.net/lists/kernel/msg2147774.html but
> did not reach Linus's next tree yet probably.

Sorry, I'll pick it now-ish...

Yours,
Linus Walleij
--
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/