All of lore.kernel.org
 help / color / mirror / Atom feed
From: Calum Mackay <calum.mackay@cdmnet.org>
To: marcelo@conectiva.com.br
Cc: calum.mackay@sun.com, mitch.dsouza@sun.com, hch@infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH]  2.4: export the symbol "mmu_cr4_features" for XFree86  DRM kernel drivers
Date: Fri, 01 Aug 2003 13:52:50 +0100	[thread overview]
Message-ID: <3F2A62A2.mailx3G211O2B4@cdmnet.org> (raw)

I'd like to request comments on the appended; proposed patch for 2.4 to
export the symbol "mmu_cr4_features".

This is needed by the XFree86 DRM kernel drivers, since Christoph's
backport of vmap() in 2.4.22-pre7. [some] DRM kernel drivers (e.g. radeon]
refuse to load without this fix, from 2.4.22-pre7 onwards.

cheers,
Calum.


[diffs -u against 2.4.22-pre9]

--- arch/i386/kernel/setup.c.20030731   2003-07-31 11:28:52.000000000 +0100
+++ arch/i386/kernel/setup.c    2003-08-01 12:42:21.000000000 +0100
@@ -128,6 +128,7 @@
 struct cpuinfo_x86 boot_cpu_data = { 0, 0, 0, 0, -1, 1, 0, 0, -1 };
 
 unsigned long mmu_cr4_features;
+EXPORT_SYMBOL(mmu_cr4_features);
 
 /*
  * Bus types ..



--- arch/x86_64/kernel/setup.c.20030731 2003-07-31 11:28:53.000000000 +0100
+++ arch/x86_64/kernel/setup.c  2003-08-01 12:43:27.000000000 +0100
@@ -30,6 +30,7 @@
 #include <linux/blk.h>
 #include <linux/highmem.h>
 #include <linux/bootmem.h>
+#include <linux/module.h>
 #include <asm/processor.h>
 #include <linux/console.h>
 #include <linux/seq_file.h>
@@ -58,6 +59,7 @@
 };
 
 unsigned long mmu_cr4_features;
+EXPORT_SYMBOL(mmu_cr4_features);
 
 /* For PCI or other memory-mapped resources */
 unsigned long pci_mem_start = 0x10000000;

             reply	other threads:[~2003-08-01 12:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 12:52 Calum Mackay [this message]
2003-08-01 13:14 ` [PATCH] 2.4: export the symbol "mmu_cr4_features" for XFree86 DRM kernel drivers Christoph Hellwig
2003-08-02 11:54   ` Calum Mackay
2003-08-02 12:34     ` Calum Mackay

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=3F2A62A2.mailx3G211O2B4@cdmnet.org \
    --to=calum.mackay@cdmnet.org \
    --cc=calum.mackay@sun.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mitch.dsouza@sun.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.