From: Valdis.Kletnieks@vt.edu
To: David Howells <dhowells@redhat.com>
Cc: jmorris@namei.org, keyrings@linux-nfs.org,
linux-nfs@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-api@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/2] Define ENOAUTHSERVICE to indicate "Authentication service unavailable"
Date: Wed, 08 Feb 2012 18:53:50 -0500 [thread overview]
Message-ID: <22934.1328745230@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 08 Feb 2012 12:29:05 GMT." <20120208122905.8902.65762.stgit@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 376 bytes --]
On Wed, 08 Feb 2012 12:29:05 GMT, David Howells said:
> +#define ENOAUTHSERVICE 139 /* Authentication service not available */
>
> #define EHWPOISON 139 /* Memory page has hardware error */
Was this an intentional overload of 139 (and so on for other archs)?
Just checking - I'm sure if it goes in like this, we'll see a patch to "fix" the
collision for 3.16.0 or so... ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2012-02-08 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 12:29 David Howells
2012-02-08 12:29 ` [PATCH 2/2] Define ENONAMESERVICE and ENAMEUNKNOWN to indicate name service errors David Howells
2012-02-08 14:15 ` Jim Rees
2012-02-09 10:04 ` David Howells
2012-02-09 13:44 ` Jim Rees
2012-02-10 20:02 ` David Howells
2012-02-08 15:48 ` [PATCH 1/2] Define ENOAUTHSERVICE to indicate "Authentication service unavailable" Joseph S. Myers
2012-02-08 23:53 ` Valdis.Kletnieks [this message]
2012-02-09 10:01 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2012-06-01 3:32 Trond Myklebust
2012-03-22 13:35 David Howells
2011-03-07 15:02 David Howells
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=22934.1328745230@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@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
all inboxes | Powered by JetHome®