From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ak@linux.intel.com, linux-kernel@vger.kernel.org
Subject: [PATCH] cpufreq/gx: Fix the compile error
Date: Mon, 30 Jan 2012 14:47:28 +0000 [thread overview]
Message-ID: <20120130144720.5908.37381.stgit@bob.linux.org.uk> (raw)
From: Alan Cox <alan@linux.intel.com>
Someone forgot to test this one it seems.
Signed-off-by: Alan Cox <alan@linux.intel.com>
---
drivers/cpufreq/gx-suspmod.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/cpufreq/gx-suspmod.c b/drivers/cpufreq/gx-suspmod.c
index 5a06c0b..456bee0 100644
--- a/drivers/cpufreq/gx-suspmod.c
+++ b/drivers/cpufreq/gx-suspmod.c
@@ -172,7 +172,7 @@ static struct pci_device_id gx_chipset_tbl[] __initdata = {
{ PCI_VDEVICE(CYRIX, PCI_DEVICE_ID_CYRIX_5510), },
{ 0, },
};
-MODULE_DEVICE_TABLE(gx_chipset_tbl);
+MODULE_DEVICE_TABLE(pci, gx_chipset_tbl);
static void gx_write_byte(int reg, int value)
{
next reply other threads:[~2012-01-30 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 14:47 Alan Cox [this message]
2012-01-30 21:07 ` [PATCH] cpufreq/gx: Fix the compile error Andi Kleen
2012-01-30 21:26 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120130144720.5908.37381.stgit@bob.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).