linux-kernel - Re: linux-next: build failure after merge of the libata 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: <AANLkTinJ8ks85Ym11wd4csdqFVgQpS7nw=RrfhMrLPUH@mail.gmail.com>
Date:	Tue, 17 Aug 2010 17:46:05 -0700
From:	Gwendal Grignou <gwendal@...gle.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, Grant Grundler <grundler@...gle.com>
Subject: Re: linux-next: build failure after merge of the libata tree

Let me fix it and send a patch to Jeff.

Gwendal.

On Tue, Aug 17, 2010 at 5:40 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Jeff,
>
> After merging the libata tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/ata/libata-transport.c: In function 'ata_attach_transport':
> drivers/ata/libata-transport.c:678: error: implicit declaration of function 'kzalloc'
> drivers/ata/libata-transport.c:678: warning: assignment makes pointer from integer without a cast
> drivers/ata/libata-transport.c: In function 'ata_release_transport':
> drivers/ata/libata-transport.c:741: error: implicit declaration of function 'kfree'
>
> Caused by commit 97395d39931160a171959ac2e1fbff1caba3374b ("[libata] Add
> ATA transport class") neglecting to include linux/slab.h.   See Rule 1 in
> Documentation/SubmitChecklist.
>
> I have used the libata tree form next-20100817 for today.
> --
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
--
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/