public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: sys_tux stolen @s390 in 2.6
Date: Thu, 19 Feb 2004 10:30:59 +0100	[thread overview]
Message-ID: <200402191030.59229.arnd@arndb.de> (raw)

Pete wrote:

> in 2.4, syscall #222 was reserved for tux on s390, but now it is used
> by sys_readahead. What do we do now?

In my copy of tux-3.2.13, the number 242 is used correctly. That number
is the one that is reserved in the official linux sources. Martin
allocated it exactly one year ago when I sent the patch enabling 
s390 in tux to Florian La Roche <laroche@redhat.com>.

If you have a really old version of the tux sources, there might
be the fallback to number 222 still there (which is a pretty dumb
idea, btw).

	Arnd <><

from tux.c:
#if defined(__powerpc__)
#define __NR_tux 225
#elif defined(__x86_64__)
#define __NR_tux 184
#elif defined(__alpha__)
#define __NR_tux 397
#elif defined(__s390__)
#define __NR_tux 242
#elif (defined (__i386__) || defined (__arm__))
#define __NR_tux 222
#else
#warning unsupported architecture, guessing __NR_tux=222 like x86...
#define __NR_tux 222
#endif


             reply	other threads:[~2004-02-19  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19  9:30 Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-19  9:56 sys_tux stolen @s390 in 2.6 Martin Schwidefsky
2004-02-19  8:53 Martin Schwidefsky
2004-02-19  0:52 Pete Zaitcev

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=200402191030.59229.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=zaitcev@redhat.com \
    /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