Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Pavel Kiryukhin <vksavl@cityline.ru>
Cc: linux-mips@linux-mips.org
Subject: Re: sys32_sched_getaffinity
Date: Tue, 20 Jan 2004 01:27:22 +0100	[thread overview]
Message-ID: <20040120002721.GA6933@linux-mips.org> (raw)
In-Reply-To: <1852455000.20040119225548@cityline.ru>

On Mon, Jan 19, 2004 at 10:55:48PM +0300, Pavel Kiryukhin wrote:

> could anybody give some comments on the following code in 2.4.x -
> 2.6.1.
> 
> sys_sched_getaffinity [kernel/sched.c] on success returns the size of
> cpumask_t, which is obviously positive value.
> 
> while
> 
> sys32_sched_getaffinity [arch/mips/kernel/linux32.c] expect 0 as
> successful return from sys_sched_getaffinity.

Wrong question.  The question should be why does the MIPS kernel not use
the generic 32-bit compatibility functions?  It now does, I just changed
that.

  Ralf

      reply	other threads:[~2004-01-20  0:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 19:55 sys32_sched_getaffinity Pavel Kiryukhin
2004-01-20  0:27 ` Ralf Baechle [this message]

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=20040120002721.GA6933@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=vksavl@cityline.ru \
    /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