From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux should define ENOTSUP
Date: Wed, 6 Dec 2006 17:14:05 +0100 [thread overview]
Message-ID: <20061206161405.GV3927@implementation.labri.fr> (raw)
In-Reply-To: <4576E355.7080708@zytor.com>
H. Peter Anvin, le Wed 06 Dec 2006 07:35:49 -0800, a écrit :
> Samuel Thibault wrote:
> >>The two can't be done at the same time. In fact, the two probably can't
> >>be done without a period of quite a few *years* between them.
> >
> >Not a reason for not doing it ;)
>
> No, but breakage is. There has to be a major benefit to justify the
> cost, and you, at least, have not provided such a justification.
Well, as I said, existing code like
switch(errno) {
case ENOTSUP:
foo();
break;
case EOPNOTSUP:
bar();
break;
}
Samuel
next prev parent reply other threads:[~2006-12-06 16:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 13:51 Linux should define ENOTSUP Samuel Thibault
2006-12-06 14:25 ` Arjan van de Ven
2006-12-06 14:31 ` Samuel Thibault
2006-12-06 15:17 ` H. Peter Anvin
2006-12-06 20:10 ` Ulrich Drepper
2006-12-06 21:11 ` H. Peter Anvin
2006-12-06 22:34 ` Ulrich Drepper
2006-12-07 13:49 ` Theodore Tso
2006-12-07 13:59 ` Andreas Schwab
2006-12-07 14:15 ` Theodore Tso
2006-12-07 14:30 ` Andreas Schwab
2006-12-07 15:33 ` Ulrich Drepper
2006-12-06 15:16 ` H. Peter Anvin
2006-12-06 15:25 ` Samuel Thibault
2006-12-06 15:26 ` H. Peter Anvin
2006-12-06 15:34 ` Samuel Thibault
2006-12-06 15:35 ` H. Peter Anvin
2006-12-06 16:14 ` Samuel Thibault [this message]
2006-12-06 16:44 ` H. Peter Anvin
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=20061206161405.GV3927@implementation.labri.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--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