From: Tigran Aivazian <tigran@veritas.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [patch-2.4.0-test12] oneliner bugfix (microcode driver again)
Date: Tue, 12 Dec 2000 10:57:50 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.21.0012121055090.924-100000@penguin.homenet> (raw)
In-Reply-To: <Pine.LNX.4.21.0012120915280.859-100000@penguin.homenet>
Hi Linus,
If misc registration fails but devfs registration succeeds then we should
return 0 from microcode_init.
Regards,
Tigran
--- linux/arch/i386/kernel/microcode.c Tue Dec 12 09:25:10 2000
+++ work/arch/i386/kernel/microcode.c Tue Dec 12 09:55:28 2000
@@ -126,6 +126,7 @@
printk(KERN_ERR "microcode: failed to devfs_register()\n");
goto out;
}
+ error = 0;
printk(KERN_INFO
"IA-32 Microcode Update Driver: v%s <tigran@veritas.com>\n",
MICROCODE_VERSION);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
parent reply other threads:[~2000-12-12 11:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.21.0012120915280.859-100000@penguin.homenet>]
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=Pine.LNX.4.21.0012121055090.924-100000@penguin.homenet \
--to=tigran@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).