From: Bernd Schmidt <bernds_cb1@t-online.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Greg KH <greg@kroah.com>,
luke.adi@gmail.com, bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: ADI Blackfin patch for kernel 2.6.14
Date: Wed, 16 Nov 2005 14:42:33 +0100 [thread overview]
Message-ID: <437B3749.5090800@t-online.de> (raw)
In-Reply-To: <20051107235035.2bdb00e1.akpm@osdl.org>
Andrew Morton wrote:
>>+asmlinkage int sys_bfin_spinlock(int *spinlock)
>
>
> Whoa, that's a syscall I never expected to see. What's it do?
Replaces the TESTSET instruction, which has a few errata that make it
unreliable. It's used by the pthreads library to provide atomic operations.
> Shouldn't
> it be using get_user() and put_user()? Or will this forever be a nommu
> arch?
We currently don't expect that this code will ever support a MMU, but I
suppose it could use get/put_user for clarity.
Bernd
next prev parent reply other threads:[~2005-11-16 13:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 9:28 ADI Blackfin patch for kernel 2.6.14 Luke Yang
2005-11-01 16:51 ` Adrian Bunk
2005-11-02 7:06 ` Luke Yang
2005-11-04 4:59 ` Luke Yang
2005-11-04 23:06 ` Greg KH
2005-11-07 6:58 ` Luke Yang
2005-11-07 16:59 ` Greg KH
2005-11-08 7:50 ` Andrew Morton
2005-11-11 11:26 ` Luke Yang
2005-11-12 11:58 ` Andrey Volkov
2005-11-14 7:22 ` Luke Yang
2005-11-12 21:47 ` Greg KH
2005-11-13 14:22 ` Bernd Schmidt
2005-11-14 7:34 ` Luke Yang
2005-11-14 7:52 ` Arjan van de Ven
2005-11-15 2:40 ` Luke Yang
2005-11-15 4:14 ` Greg KH
2005-11-14 12:53 ` Alan Cox
2005-11-16 3:44 ` Luke Yang
2005-11-16 6:11 ` Paul Jackson
2005-11-16 6:34 ` Luke Yang
2005-11-16 13:42 ` Bernd Schmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 20:53 Robin Getz
2005-11-15 19:11 ` Matthieu CASTET
2005-11-17 5:38 Robin Getz
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=437B3749.5090800@t-online.de \
--to=bernds_cb1@t-online.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox