public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: Kernel/Glibc: EOPNOTSUPP vs. ENOTSUP vs. ENOTSUPP (also [RFC] POSIX ACL kernel infrastructure)
Date: 4 Aug 2002 11:32:12 -0700	[thread overview]
Message-ID: <aijrvc$al5$1@cesium.transmeta.com> (raw)
In-Reply-To: 20020804154628.A28845@infradead.org

Followup to:  <20020804154628.A28845@infradead.org>
By author:    Christoph Hellwig <hch@infradead.org>
In newsgroup: linux.dev.fs.devel
>
> On Sun, Aug 04, 2002 at 03:46:47PM +0200, Andreas Gruenbacher wrote:
> > The standard further says the numbers assigned to ENOTSUP and EOPNOTSUPP
> >  shall be unique.
> 
> Where?  I can't find it in my copy of 1003.1eD17
> 

In the final version of 1003.1:2001, it is at the Base definitions
volume, page 217, line 7687:

7686 The <errno.h> header shall provide a declaration for errno and
     give positive values for the
7687 following symbolic constants. Their values shall be unique except
     as noted below.

[ENOTSUP] and [EOPNOTSUPP] are both listed without allowing the
numbers to be aliased.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2002-08-04 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04 13:46 Kernel/Glibc: EOPNOTSUPP vs. ENOTSUP vs. ENOTSUPP (also [RFC] POSIX ACL kernel infrastructure) Andreas Gruenbacher
2002-08-04 14:46 ` Christoph Hellwig
2002-08-04 18:32   ` H. Peter Anvin [this message]
2002-08-05  8:38   ` Andreas Gruenbacher

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='aijrvc$al5$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-fsdevel@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