linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org, torvalds@transemta.com
Subject: Patch: linux-2.4.0-pre1/arch/i386/i386_ksyms.c needs to export mmu_cr4_features
Date: Tue, 9 Jan 2001 21:06:25 -0800	[thread overview]
Message-ID: <20010109210625.A2924@adam.yggdrasil.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]


	linux-2.4.1-pre1/drivers/md/xor.c calls the macro XOR_TRY_TEMPLATES,
which is defined in include/asm-i386/xor.h to use HAVE_XMM, which is
defined in include/asm-i386/processor.h to reference mmu_cr4_features.
So, to support compilation of raid5 as a module, i386_ksyms.c needs
to export mmu_cr4_features.  I have attached the one line patch below.

	Let me also add that 2.4.1-pre1 so far has been really smooth
sailing.  The problems with 2.4.0 hanging on the Sony PictureBook PCG-C1VN
have somehow disappeared with this version, usb-uhci.c does not generate
a kernel oops on that hardware, and this minor addition to i386_ksyms.c
was the only change that I had to make to get a clean build.  Hooray!

-- 
Adam J. Richter     __     ______________   4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com     \ /                  San Jose, California 95129-1034
+1 408 261-6630         | g g d r a s i l   United States of America
fax +1 408 261-6631      "Free Software For The Rest Of Us."

[-- Attachment #2: ksyms.diff --]
[-- Type: text/plain, Size: 314 bytes --]

--- linux-2.4.1-pre1/arch/i386/kernel/i386_ksyms.c	Wed Dec  6 21:00:12 2000
+++ linux/arch/i386/kernel/i386_ksyms.c	Tue Jan  9 15:46:14 2001
@@ -49,6 +50,7 @@
 
 /* platform dependent support */
 EXPORT_SYMBOL(boot_cpu_data);
+EXPORT_SYMBOL(mmu_cr4_features);
 #ifdef CONFIG_EISA
 EXPORT_SYMBOL(EISA_bus);
 #endif

                 reply	other threads:[~2001-01-10  5:06 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=20010109210625.A2924@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transemta.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).