All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Kohl <jtk@rational.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] [re-send] more missing symbols (test12 patch)?
Date: Tue, 02 Jan 2001 15:30:36 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205877@msgid-missing> (raw)

I'm resending this again, as the list seems to be dead or comatose at
least (if anybody at linuxia64.org is reading this, please fix the list
and its archives).

Date: Mon, 18 Dec 2000 15:20:48 -0500 (EST)
From: John Kohl <jtk@rational.com>
To: linux-ia64@linuxia64.org
Subject: more missing symbols (test12 patch)?

These look like more missing symbol exports from the test12-based patch
kit.  I'm presuming they should be exported without versions, similarly
to what i386 does with its locking-related exports?

#include <asm/semaphore.h>
EXPORT_SYMBOL_NOVERS(__down);
EXPORT_SYMBOL_NOVERS(__down_interruptible);
EXPORT_SYMBOL_NOVERS(__down_trylock);
EXPORT_SYMBOL_NOVERS(__up);
EXPORT_SYMBOL_NOVERS(__down_read_failed);
EXPORT_SYMBOL_NOVERS(__down_write_failed);
EXPORT_SYMBOL_NOVERS(__rwsem_wake);

p.s. we got test12 kernels running on our Big Sur system, after
upgrading to BIOS 60.  (It took a while to determine that our processors
are A2 stepping, and we're arranging to get upgrades soon.)
Thanks for all the suggestions!

-- 
=John Kohl <jtk@rational.com>, Software Engineer
Rational Software, Configuration Management Business Unit
Mark your calendars!  Rational User Conference 2001, July 22-26, 2001
in beautiful Denver, Colorado


             reply	other threads:[~2001-01-02 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02 15:30 John Kohl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-19 23:24 [Linux-ia64] [re-send] more missing symbols (test12 patch)? John Kohl

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=marc-linux-ia64-105590678205877@msgid-missing \
    --to=jtk@rational.com \
    --cc=linux-ia64@vger.kernel.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 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.