From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@osdl.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
linux-kernel@vger.kernel.org, fastboot@osdl.org
Subject: [PATCH] i386 apic: Fix mispelling of APIC
Date: Wed, 05 Oct 2005 12:30:20 -0600 [thread overview]
Message-ID: <m1ek6z7r5v.fsf_-_@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.61L.0510041811590.10696@blysk.ds.pg.gda.pl> (Maciej W. Rozycki's message of "Tue, 4 Oct 2005 18:16:36 +0100 (BST)")
"Maciej W. Rozycki" <macro@linux-mips.org> writes:
>> So what should the capitalization be? "APIC disabled\n" ?
>
> Obviously. Thanks for your tidy-up!
Welcome.
Looking a little deeper I just copied the mispelling from x86_64.
Here is the incremental patch that fixes the i386 version.
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
---
arch/i386/kernel/apic.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
7edc564590555e94268fb73ddf97431b4b9df945
diff --git a/arch/i386/kernel/apic.c b/arch/i386/kernel/apic.c
--- a/arch/i386/kernel/apic.c
+++ b/arch/i386/kernel/apic.c
@@ -1265,7 +1265,7 @@ fastcall void smp_error_interrupt(struct
int __init APIC_init(void)
{
if (enable_local_apic < 0) {
- printk(KERN_INFO "Apic disabled\n");
+ printk(KERN_INFO "APIC disabled\n");
return -1;
}
next prev parent reply other threads:[~2005-10-05 18:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 15:04 [PATCH] i386: move apic init in init_IRQs Eric W. Biederman
2005-10-04 15:34 ` Maciej W. Rozycki
2005-10-04 15:48 ` Eric W. Biederman
2005-10-04 17:16 ` Maciej W. Rozycki
2005-10-05 18:30 ` Eric W. Biederman [this message]
2005-10-21 13:33 ` [Fastboot] " Vivek Goyal
2005-10-21 14:45 ` Eric W. Biederman
2005-10-21 16:53 ` Albert Herranz
2005-10-21 18:01 ` Eric W. Biederman
2005-10-22 14:52 ` Vivek Goyal
2005-10-22 15:23 ` Eric W. Biederman
2005-10-24 13:03 ` Vivek Goyal
2005-10-24 15:36 ` Eric W. Biederman
2005-10-25 7:17 ` Eric W. Biederman
2005-10-25 7:47 ` [PATCH] i386 mpparse: Only ignore lapic information we can't store Eric W. Biederman
2005-10-25 9:42 ` Vivek Goyal
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=m1ek6z7r5v.fsf_-_@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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®