linux-kernel - Re: linux-next: build failure after merge of the acpi 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] [day] [month] [year] [list]

Date:	Thu, 2 Aug 2012 10:00:22 +0800
From:	Feng Tang <feng.tang@...el.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Len Brown <lenb@...nel.org>, <linux-next@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, Joerg Roedel <joro@...tes.org>
Subject: Re: linux-next: build failure after merge of the acpi tree

On Thu, 2 Aug 2012 11:20:33 +1000
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Len,
> 
> After merging the acpi tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/iommu/amd_iommu_init.c: In function 'early_amd_iommu_init':
> drivers/iommu/amd_iommu_init.c:1535:2: error: implicit declaration of
> function 'acpi_get_table_with_size' [-Werror=implicit-function-declaration]
> 
> Caused by commit 705d9245d714 ("ACPI: remove acpi_get_table_with_size()
> fucntion").
> 
> This extra call to acpi_get_table_with_size() was added by commit
> 02f3b3f5449c ("iommu/amd: Use acpi_get_table instead of
> acpi_table_parse") added to Linus' tree on about July 25 via the iommu
> tree.

Thanks for the root cause, Yinghai also noticed me about that, and I've
send a updated patch 
	https://lkml.org/lkml/2012/8/1/25 

So it should be ok after Len merge this v2 patch.

Thanks,
Feng

> 
> I have reverted the acpi tree commit for today.
--
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/