All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Hanley <sjh@svana.org>
To: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: [patch] missing exported symbols
Date: Sun, 21 Jan 2001 14:40:57 +1100	[thread overview]
Message-ID: <20010121144057.A27643@wibble.net> (raw)


All

I had to add these two symbol exports to this file.

The first one I have noticed was not available for the last few weks or so
of 2.4.0 and 2.4.0-pre kernels. The second one I only noticed today when I
tried to build the gmac as a module.

The first one I am pretty sure belongs in this file as i have noticed a few
other archs have to export it here.

The gmac one i am unsure if this is the best place to put the export, but it
works so I put it here.

Most if not all filesystems need the flush_dcache_page exported if they are
built as modules. The gmac thing needs to be exported if gmac is built as a
module.

This is from a paulus 2.4.0 rsynced yesterday (saturday AEST).

--- old/linux-pmac-devel/arch/ppc/kernel/ppc_ksyms.c    Tue Jan  9 14:49:03 2001
+++ linux-pmac-devel/arch/ppc/kernel/ppc_ksyms.c        Sun Jan 21 13:07:08 2001
@@ -364,3 +364,7 @@
 EXPORT_SYMBOL_NOVERS(__no_use_restore_flags);
 EXPORT_SYMBOL_NOVERS(__no_use_save_flags);
 #endif
+
+/* needed by some modules */
+EXPORT_SYMBOL(flush_dcache_page);
+EXPORT_SYMBOL(feature_set_gmac_phy_reset);

	See You
	    Steve

--
sjh@wibble.net http://wibble.net/~sjh/
Look Up In The Sky
   Is it a bird?  No
      Is it a plane?  No
         Is it a small blue banana?
YES

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-01-21  3:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-21  3:40 Steven Hanley [this message]
2001-01-21 21:28 ` [patch] missing exported symbols Tom Rini
2001-01-21 22:11   ` Steven Hanley
2001-01-21 22:42     ` Tom Rini

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=20010121144057.A27643@wibble.net \
    --to=sjh@svana.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sjh@wibble.net \
    /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.