From: "tip-bot for H. Peter Anvin" <hpa@linux.intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
florian@openwrt.org, mark@bifferos.com, tglx@linutronix.de,
hpa@linux.intel.com
Subject: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c_ident is
Date: Tue, 3 Aug 2010 17:49:02 GMT [thread overview]
Message-ID: <tip-c0366f5f5c1615c4f70b1bd646149ba9233830b9@git.kernel.org> (raw)
In-Reply-To: <201008031815.09764.florian@openwrt.org>
Commit-ID: c0366f5f5c1615c4f70b1bd646149ba9233830b9
Gitweb: http://git.kernel.org/tip/c0366f5f5c1615c4f70b1bd646149ba9233830b9
Author: H. Peter Anvin <hpa@linux.intel.com>
AuthorDate: Tue, 3 Aug 2010 10:09:56 -0700
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Tue, 3 Aug 2010 10:09:56 -0700
x86, cpu: RDC doesn't have CPUID, which is what c_ident is
c_ident is supposed to be a CPUID identifier, and RDC doesn't have
that.
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: Mark Kelly <mark@bifferos.com>
Cc: Florian Fainelli <florian@openwrt.org>
LKML-Reference: <201008031815.09764.florian@openwrt.org>
---
arch/x86/kernel/cpu/rdc.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/cpu/rdc.c b/arch/x86/kernel/cpu/rdc.c
index c2bcdcc..e5e241c 100644
--- a/arch/x86/kernel/cpu/rdc.c
+++ b/arch/x86/kernel/cpu/rdc.c
@@ -65,7 +65,6 @@ static void __cpuinit rdc_identify(struct cpuinfo_x86 *c)
static const struct cpu_dev __cpuinitconst rdc_cpu_dev = {
.c_vendor = "RDC",
- .c_ident = { "RDC" },
.c_identify = rdc_identify,
.c_x86_vendor = X86_VENDOR_RDC,
};
next prev parent reply other threads:[~2010-08-03 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201008031815.09764.florian@openwrt.org>
2010-08-03 17:48 ` [tip:x86/cpu] x86, cpu: CPU detection for RDC System-on-Chip tip-bot for Mark Kelly
2010-08-03 17:49 ` tip-bot for H. Peter Anvin [this message]
2010-08-03 19:25 ` [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c_ident is Ingo Molnar
2010-08-04 9:12 ` bifferos
2010-08-04 9:25 ` Ingo Molnar
2010-08-04 20:14 ` H. Peter Anvin
2010-08-04 22:59 ` bifferos
2010-08-04 23:09 ` H. Peter Anvin
2010-08-05 0:27 ` bifferos
2010-08-05 2:00 ` H. Peter Anvin
2010-08-09 9:33 ` bifferos
2010-08-09 20:15 ` H. Peter Anvin
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=tip-c0366f5f5c1615c4f70b1bd646149ba9233830b9@git.kernel.org \
--to=hpa@linux.intel.com \
--cc=florian@openwrt.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mark@bifferos.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome