From: Linus Walleij <linus.walleij@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Bjorn Andersson <Bjorn.Andersson@sonymobile.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: Tree for Feb 17 (pinctrl-msm)
Date: Mon, 24 Feb 2014 15:46:17 +0100 [thread overview]
Message-ID: <CACRpkdamW1-CxZV65at3PaPhY5nANRDd=SY=FsNPVnrPxyD81w@mail.gmail.com> (raw)
In-Reply-To: <530247FC.90606@infradead.org>
On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap <rdunlap@infradead.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@kernel.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?
Yours,
Linus Walleij
next prev parent reply other threads:[~2014-02-24 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 6:23 linux-next: Tree for Feb 17 Stephen Rothwell
2014-02-17 17:33 ` linux-next: Tree for Feb 17 (pinctrl-msm) Randy Dunlap
2014-02-24 14:46 ` Linus Walleij [this message]
2014-02-24 17:46 ` Bjorn Andersson
2014-02-24 18:14 ` Randy Dunlap
2014-02-24 18:41 ` Josh Cartwright
2014-02-24 18:46 ` Randy Dunlap
2014-02-24 19:28 ` Bjorn Andersson
2014-02-25 9:44 ` Linus Walleij
2014-02-25 9:39 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACRpkdamW1-CxZV65at3PaPhY5nANRDd=SY=FsNPVnrPxyD81w@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).