linux-kernel - Re: linux-next: Tree for Feb 17 (pinctrl-msm)

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: <530B8C15.50100@infradead.org>
Date:	Mon, 24 Feb 2014 10:14:45 -0800
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Bjorn Andersson <bjorn.andersson@...ymobile.com>,
	Linus Walleij <linus.walleij@...aro.org>
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>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: linux-next: Tree for Feb 17 (pinctrl-msm)

On 02/24/2014 09:46 AM, Bjorn Andersson wrote:
> On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote:
> 
>> On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap <rdunlap@...radead.org> wrote:
>>> On 02/16/2014 10:23 PM, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> If you see failures in building this tree due to missing declarations of
>>>> k..alloc/free, then it may be caused by commit 2bd59d48ebfb ("cgroup:
>>>> convert to kernfs").  Please send Tejun Heo <tj@...nel.org> a patch
>>>> adding an inclusion of linux/slab.h to the appropriate file(s).
>>>>
>>>> This tree fails (more than usual) the powerpc allyesconfig build.
>>>>
>>>> Changes since 20140214:
>>>>
>>>
>>> on i386:
>>>
>>> ERROR: "handle_bad_irq" [drivers/pinctrl/pinctrl-msm.ko] undefined!
>>
>> Weird, Björn do you know what may be causing this?
> 
> I include linux/irq.h to get hold of handle_bad_irq() and as far as I can see
> there are no changes related to that in linux-next.
> 
> Do we know if the build still fails? Or if something changed?
> 
> 
> Please let me know if I should pull down the -next tree and try to reproduce
> this.

I guess that you get off free on this one since I didn't post the failing
.config file and I have already deleted it.

I'm trying to reproduce it now but it's slow going.  I'll let you know if
I get it to fail again.

thanks,
-- 
~Randy
--
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/