linux-kernel - Re: [PATCH] ata_piix: Fix build breakage

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: <C9402502-28EB-4D08-ABEE-12E17B031E31@kernel.crashing.org>
Date:	Wed, 28 Jan 2009 00:08:39 -0600
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Kumar Gala <galak@...nel.crashing.org>
Cc:	jeff@...zik.org, Linus Torvalds <torvalds@...l.org>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	rjw@...k.pl
Subject: Re: [PATCH] ata_piix: Fix build breakage


On Jan 27, 2009, at 11:02 PM, Kumar Gala wrote:

> The following commit introduces:
>
> commit 5f451fe1ab5d73b987051f0d23c85216c552e163
> Author: Rafael J. Wysocki <rjw@...k.pl>
> Date:   Mon Jan 19 20:59:22 2009 +0100
>
>    SATA PIIX: Blacklist system that spins off disks during ACPI  
> power off
>
> the following build errors on non-x86 systems:
>
> drivers/ata/ata_piix.c: In function 'piix_broken_system_poweroff':
> drivers/ata/ata_piix.c:1405: error: implicit declaration of function  
> 'dmi_first_match'
> drivers/ata/ata_piix.c:1405: warning: initialization makes pointer  
> from integer without a cast
>
> Signed-off-by: Kumar Gala <galak@...nel.crashing.org>
> ---
> drivers/ata/ata_piix.c |    2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)


it was pointed out that fixing include/linux/dmi.h was the better way  
to fix this.  I've posted a patch for fixing dmi.h that supersedes  
this patch.

- k
--
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/