From: david singleton <dsingleton@mvista.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: akpm@osdl.org, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [robust-futex-1] futex: robust futex support
Date: Sat, 14 Jan 2006 16:04:10 -0800 [thread overview]
Message-ID: <746DBAD6-855A-11DA-A824-000A959BB91E@mvista.com> (raw)
In-Reply-To: <a36005b50601141602y641567ebh5ff9b6a1fad4d7d2@mail.gmail.com>
On Jan 14, 2006, at 4:02 PM, Ulrich Drepper wrote:
> On 1/13/06, David Singleton <dsingleton@mvista.com> wrote:
> =============================================
>> --- linux-2.6.15.orig/include/asm-generic/errno.h
>> +++ linux-2.6.15/include/asm-generic/errno.h
>> @@ -105,5 +105,6 @@
>> /* for robust mutexes */
>> #define EOWNERDEAD 130 /* Owner died */
>> #define ENOTRECOVERABLE 131 /* State not recoverable */
>> +#define ENOTSHARED 132 /* no pshared attribute */
>
> Do not introduce a new error code if at all possible. Adding
> userlang-visible error codes means the ABI changes due to the stupid
> _sys_errlist variable. Just reuse an error code which cannot be
> returned in the futex code so far and which has some kind of
> resemblence with what the error means.
can you suggest some error codes you like to use? I'll use
whatever you suggest.
thanks
David
next prev parent reply other threads:[~2006-01-15 0:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 1:00 [robust-futex-1] futex: robust futex support David Singleton
2006-01-15 0:02 ` Ulrich Drepper
2006-01-15 0:04 ` david singleton [this message]
2006-01-15 5:18 ` Ulrich Drepper
2006-01-15 20:00 ` David Singleton
2006-01-17 2:27 ` [robust-futex-3] " david singleton
2006-01-17 17:32 ` Ulrich Drepper
2006-01-17 17:50 ` Ulrich Drepper
2006-01-19 2:26 ` [robust-futex-4] " david singleton
2006-01-19 5:22 ` Andrew Morton
2006-01-20 0:47 ` [robust-futex-5] " david singleton
2006-01-20 17:41 ` [robust-futex-4] " Ingo Oeser
2006-01-20 22:18 ` Andrew Morton
2006-01-21 2:30 ` david singleton
2006-01-23 18:20 ` Todd Kneisel
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=746DBAD6-855A-11DA-A824-000A959BB91E@mvista.com \
--to=dsingleton@mvista.com \
--cc=akpm@osdl.org \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).