From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Tejun Heo <tj@kernel.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Hicks <mort@sgi.com>
Subject: Re: linux-next: build failure after merge of the slabh tree
Date: Tue, 30 Mar 2010 14:32:59 -0500 [thread overview]
Message-ID: <4BB251EB.5010008@windriver.com> (raw)
In-Reply-To: <20100329160248.e15e7836.sfr@canb.auug.org.au>
On 03/29/2010 12:02 AM, Stephen Rothwell wrote:
> Hi Tejun,
>
> After merging the slabh tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> kernel/debug/kdb/kdb_support.c: In function 'kdb_strdup':
> kernel/debug/kdb/kdb_support.c:309: error: implicit declaration of function 'kmalloc'
> kernel/debug/kdb/kdb_support.c:309: warning: initialization makes pointer from integer without a cast
> kernel/debug/kdb/kdb_support.c: In function 'debug_kfree':
> kernel/debug/kdb/kdb_support.c:810: error: implicit declaration of function 'kfree'
>
> Caused by commit d103d3b3e8512312b5254950035366d4422a479a ("percpu: don't
> implicitly include slab.h from percpu.h") from the slabh tree interacting
> with commit 5572dd736e5577dfefafe2ad3b54760e8323e33d ("kdb: core for kgdb
> back end (1 of 2)") from the kgdb tree.
>
> I applied the following merge fixup patch which should be applied to the
> kdbg tree (see Documentation/SubmitChecklist Rule #1 :-)).
>
>
But of course.
This is applied and will appear in kgdb-next in the next hour.
Thanks,
Jason.
next prev parent reply other threads:[~2010-03-30 19:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 5:02 linux-next: build failure after merge of the slabh tree Stephen Rothwell
2010-03-30 19:32 ` Jason Wessel [this message]
2010-03-30 22:49 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-04-01 5:41 Stephen Rothwell
2010-04-01 7:29 ` David Miller
2010-04-01 7:31 ` Tejun Heo
2010-04-01 7:40 ` Stephen Rothwell
2010-03-29 6:55 Stephen Rothwell
2010-03-29 7:34 ` Takashi Iwai
2010-03-29 6:07 Stephen Rothwell
2010-05-19 16:23 ` Stephen Rothwell
2010-03-29 5:59 Stephen Rothwell
2010-03-29 5:53 Stephen Rothwell
2010-03-29 5:47 Stephen Rothwell
2010-03-29 5:39 Stephen Rothwell
2010-03-29 5:34 Stephen Rothwell
2010-03-29 5:29 Stephen Rothwell
2010-03-29 5:28 Stephen Rothwell
2010-03-29 5:28 Stephen Rothwell
2010-03-29 5:02 Stephen Rothwell
2010-03-29 22:33 ` Dan Williams
2010-03-29 23:16 ` Stephen Rothwell
2010-03-29 5:02 Stephen Rothwell
2010-03-29 6:28 ` Takashi Iwai
2010-03-29 6:38 ` Stephen Rothwell
2010-03-29 8:01 ` Stephen Rothwell
2010-03-29 8:05 ` Takashi Iwai
2010-03-29 11:10 ` Tejun Heo
2010-03-29 12:25 ` Stephen Rothwell
2010-03-29 4:42 Stephen Rothwell
2010-03-30 12:14 ` Jon Masters
2010-03-30 13:45 ` Stephen Rothwell
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=4BB251EB.5010008@windriver.com \
--to=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mort@sgi.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
/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).