All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guy Martin <gmsoft@tuxicoman.be>
To: linux-parisc@vger.kernel.org
Subject: [PATCH] Make EWOULDBLOCK be equal to EAGAIN on parisc.
Date: Thu, 16 Jan 2014 17:17:53 +0100	[thread overview]
Message-ID: <7b86ec9f26dd9a18e7fae7a39e6a3382@tuxicoman.be> (raw)

On Linux, only parisc uses a different value for EWOULDBLOCK which
causes a lot of troubles for applications not checking for both values.
Since the hpux compat is long dead, make EWOULDBLOCK behave the same as
all other architectures.

Signed-off-by: Guy Martin  <gmsoft@tuxicoman.be>
---
  arch/parisc/include/uapi/asm/errno.h | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/parisc/include/uapi/asm/errno.h 
b/arch/parisc/include/uapi/asm/errno.h
index f3a8aa5..c0ae625 100644
--- a/arch/parisc/include/uapi/asm/errno.h
+++ b/arch/parisc/include/uapi/asm/errno.h
@@ -106,7 +106,7 @@

  #define	EALREADY	244	/* Operation already in progress */
  #define	EINPROGRESS	245	/* Operation now in progress */
-#define	EWOULDBLOCK	246	/* Operation would block (Linux returns EAGAIN) 
*/
+#define	EWOULDBLOCK	EAGAIN	/* Operation would block (Not HPUX 
compliant) */
  #define	ENOTEMPTY	247	/* Directory not empty */
  #define	ENAMETOOLONG	248	/* File name too long */
  #define	ELOOP		249	/* Too many symbolic links encountered */
-- 
1.8.3.2


             reply	other threads:[~2014-01-16 16:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 16:17 Guy Martin [this message]
2014-01-16 20:02 ` [PATCH] Make EWOULDBLOCK be equal to EAGAIN on parisc Carlos O'Donell
2014-01-16 20:49   ` John David Anglin
2014-01-16 21:05     ` Carlos O'Donell
2014-01-16 21:15       ` Helge Deller
2014-01-16 22:43         ` Mike Frysinger
2014-01-17  8:55         ` Guy Martin
2014-01-17 14:01           ` John David Anglin
2014-01-17 14:08             ` Carlos O'Donell
2014-01-17 15:11               ` Guy Martin
2014-01-17 22:27                 ` Helge Deller
2014-01-31 16:53 ` Helge Deller
2014-01-31 17:24   ` Carlos O'Donell
2014-01-31 23:16     ` Mike Frysinger

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=7b86ec9f26dd9a18e7fae7a39e6a3382@tuxicoman.be \
    --to=gmsoft@tuxicoman.be \
    --cc=linux-parisc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.