From: Ioannis Barkas <risc4all@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] amd.c: Corrected broken URL and display the same units at all messages
Date: Tue, 26 Jun 2007 02:04:06 -0700 (PDT) [thread overview]
Message-ID: <891163.25673.qm@web63512.mail.re1.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
Fixes two messages displaying Megabit (Mb) instead of
Megabyte (MB) and updates URLs.
Hello we are Ioannis Barkas (risc4all@yahoo.com) and
Nikos Barkas (doubl3nuts@yahoo.com).
The printed messages behaviour is not consistent as
one message is printed
with MB and the next two are printed with Mb.Also a
link is broken.
We sent the patch from diff -u as an attachment
because damn yahoo...can't even format an inline patch!
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545433
[-- Attachment #2: 1728711821-diff2.log --]
[-- Type: application/octet-stream, Size: 1746 bytes --]
--- /linux-2.6.21/arch/i386/kernel/cpu/amd.c 2007-04-26 04:08:32.000000000 -0400
+++ /linux/arch/i386/kernel/cpu/amd.c 2007-06-26 11:18:25.000000000 -0400
@@ -9,10 +9,12 @@
/*
* B step AMD K6 before B 9730xxxx have hardware bugs that can cause
* misexecution of code under Linux. Owners of such processors should
- * contact AMD for precise details and a CPU swap.
+ * contact AMD for precise details and a CPU swap. More information can
+ * be found at erratum 2.6.2 of 21266.pdf.
*
* See http://www.multimania.com/poulot/k6bug.html
- * http://www.amd.com/K6/k6docs/revgd.html
+ * http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_739_1102,00.html
+ * http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/21266.pdf
*
* The following test is erm.. interesting. AMD neglected to up
* the chip setting when fixing the bug but they also tweaked some
@@ -146,7 +148,7 @@
/* K6 with old style WHCR */
if (c->x86_model < 8 ||
(c->x86_model== 8 && c->x86_mask < 8)) {
- /* We can only write allocate on the low 508Mb */
+ /* We can only write allocate on the low 508MB */
if(mbytes>508)
mbytes=508;
@@ -158,7 +160,7 @@
wbinvd();
wrmsr(MSR_K6_WHCR, l, h);
local_irq_restore(flags);
- printk(KERN_INFO "Enabling old style K6 write allocation for %d Mb\n",
+ printk(KERN_INFO "Enabling old style K6 write allocation for %d MB\n",
mbytes);
}
break;
@@ -179,7 +181,7 @@
wbinvd();
wrmsr(MSR_K6_WHCR, l, h);
local_irq_restore(flags);
- printk(KERN_INFO "Enabling new style K6 write allocation for %d Mb\n",
+ printk(KERN_INFO "Enabling new style K6 write allocation for %d MB\n",
mbytes);
}
reply other threads:[~2007-06-26 9:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=891163.25673.qm@web63512.mail.re1.yahoo.com \
--to=risc4all@yahoo.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
all inboxes | Powered by JetHome®