linux-kernel - [PATCH -next] cpufreq: fix gx-suspmod.c build

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: <4F26F242.1060903@xenotime.net>
Date:	Mon, 30 Jan 2012 11:40:50 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Hiroshi Miura <miura@...cha.org>,
	Dave Jones <davej@...hat.com>, cpufreq@...r.kernel.org
Subject: [PATCH -next] cpufreq: fix gx-suspmod.c build

From: Randy Dunlap <rdunlap@...otime.net>

Fix build error & warnings:

drivers/cpufreq/gx-suspmod.c:175:35: error: macro "MODULE_DEVICE_TABLE" requires 2 arguments, but only 1 given
drivers/cpufreq/gx-suspmod.c:175:1: warning: data definition has no type or storage class
drivers/cpufreq/gx-suspmod.c:175:1: warning: type defaults to 'int' in declaration of 'MODULE_DEVICE_TABLE'

Signed-off-by: Randy Dunlap <rdunlap@...otime.net>
Cc: Hiroshi Miura <miura@...cha.org>
Cc:	Dave Jones <davej@...hat.com>
Cc:	cpufreq@...r.kernel.org
---
 drivers/cpufreq/gx-suspmod.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20120130.orig/drivers/cpufreq/gx-suspmod.c
+++ linux-next-20120130/drivers/cpufreq/gx-suspmod.c
@@ -172,7 +172,7 @@ static struct pci_device_id gx_chipset_t
 	{ PCI_VDEVICE(CYRIX, PCI_DEVICE_ID_CYRIX_5510), },
 	{ 0, },
 };
-MODULE_DEVICE_TABLE(gx_chipset_tbl);
+MODULE_DEVICE_TABLE(x86cpu, gx_chipset_tbl);
 
 static void gx_write_byte(int reg, int value)
 {
--
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/