public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: leif <leif@gci.net>
To: "'Andrew Morton'" <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: RE: error in Sparc64 rwlock.S
Date: Wed, 19 Nov 2003 12:37:33 -0900	[thread overview]
Message-ID: <014401c3aee5$587aea20$31828ad0@internet.gci.net> (raw)
In-Reply-To: <20031118130956.1edd4a24.akpm@osdl.org>

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

Andrew Morton writes:
> leif <leif@gci.net> wrote:
>>
>> I'm going through the 2.6.0-test9 and some -mm3 patches, 
>> and have run into an issue with arch/sparc64/lib/rwlock.S
>> 
>> When compiling, the assembler complains of multiple
>> definitions of  __write_trylock.
> 
> OK, the lockmeter patch adds a write_trylock() implementation 
> to sparc64, but now Linus's tree has one anyway.
> 
> Does this fix it?

Now there's a different problem...

Error: local label '"100" (instance number 1 of a fb label)'
  is not defined

Should I try to grab a different -test9  bk version out of
Linus' tree?

If so, where would I look -- i've not been keeping up with
the bk info/requirements


Leif

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2208 bytes --]

  parent reply	other threads:[~2003-11-19 21:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 20:43 Linux 2.4.20-ac2 Alan Cox
2002-12-11 23:30 ` HyperThreading in recent 2.4-ac kernels Gerald Britton
2002-12-12  1:36   ` Alan Cox
2002-12-12 20:12   ` detecting layout in RAID Anu
2002-12-17 22:55     ` Neil Brown
2003-11-18 21:01 ` error in Sparc64 rwlock.S leif
2003-11-18 21:09   ` Andrew Morton
2003-11-19  0:46     ` David S. Miller
2003-11-19 21:37     ` leif [this message]
2003-11-19 22:30       ` Andrew Morton
2003-11-20  0:03         ` leif

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='014401c3aee5$587aea20$31828ad0@internet.gci.net' \
    --to=leif@gci.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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