linux-kernel - Re: linux-next: build failure after merge of the slabh 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: <e9c3a7c21003291533w3c672371o87db6aad8bac7ef2@mail.gmail.com>
Date:	Mon, 29 Mar 2010 15:33:25 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Tejun Heo <tj@...nel.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Richard Röjfors" 
	<richard.rojfors@...agicore.com>
Subject: Re: linux-next: build failure after merge of the slabh tree

On Sun, Mar 28, 2010 at 10:02 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Tejun,
>
> After merging the slabh tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/dma/timb_dma.c: In function 'td_alloc_init_desc':
> drivers/dma/timb_dma.c:381: error: implicit declaration of function 'kzalloc'
> drivers/dma/timb_dma.c:381: warning: assignment makes pointer from integer without a cast
> drivers/dma/timb_dma.c:389: warning: assignment makes pointer from integer without a cast
> drivers/dma/timb_dma.c:410: error: implicit declaration of function 'kfree'
> drivers/dma/timb_dma.c: In function 'td_probe':
> drivers/dma/timb_dma.c:710: warning: assignment makes pointer from integer without a cast
>
> Caused by commit d103d3b3e8512312b5254950035366d4422a479a ("percpu: don't
> implicitly include slab.h from percpu.h") from the slabh tree interacting
> with commit de5d4453c5b224eefd02b6a141ed411a76d458af ("dma: Add
> timb-dma") from the async_tx tree.
>
> I applied the following merge fixup patch which should be applied to the
> async_tx tree (see Documentation/SubmitChecklist Rule #1 :-)).

Thanks, noted and applied.
--
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/