public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Noah Romer <nromer@lsil.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] rwlock and atomic_sub on ia64
Date: Tue, 14 Aug 2001 21:00:39 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805079@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805063@msgid-missing>

David Mosberger wrote:
 >>>>>>On 13 Aug 2001 22:48:11 +0200, Jes Sorensen <jes@sunsite.dk> said:
 >>>>>>
 >
 >   Jes> I'll leave the question about rwsem's to David ;)
 >
 > We're using the generic implementation on ia64.
 >
 > 	--david
 >

Yes, but how do I get to it? I finally found the ia64 implementation of
write_lock and read_lock for SMP systems (which is what I'm compiling
on).(1) However, when I try to compile the driver I get a

   warning: implicit declaration of function `rwlock_init'

message. I have <linux/spinlock.h> included, and that's been enough up 
until now. Is there someother include file I need under the ia64 arch?

Thanks.


(1) Source Navigator doesn't seem to find it when I just have it look
for functions/macros w/ those names, but it does find the rwlock_t
declaration in include/asm-ia64/spinlock.h.

-- 
Noah Romer
Driver Developer, CM gopher and Linux Whipping Boy
Storage Components Firmware
LSI Logic Corp.




  parent reply	other threads:[~2001-08-14 21:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 13:55 [Linux-ia64] rwlock and atomic_sub on ia64 Noah Romer
2001-08-13 17:02 ` Jes Sorensen
2001-08-13 20:40 ` Noah Romer
2001-08-13 20:48 ` Jes Sorensen
2001-08-13 20:54 ` Noah Romer
2001-08-13 20:55 ` David Mosberger
2001-08-14 21:00 ` Noah Romer [this message]
2001-08-15 18:37 ` David Mosberger
2001-08-15 20:30 ` Noah Romer
2001-08-15 22:29 ` KOCHI Takayoshi
2001-08-16  0:25 ` David Mosberger

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-105590698805079@msgid-missing \
    --to=nromer@lsil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox