From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-arch@vger.kernel.org
Subject: Re: RFC: remove ibcs2/PER_SVR4?
Date: Wed, 01 Oct 2008 18:17:41 +0200 [thread overview]
Message-ID: <1222877861.32562.14.camel@localhost> (raw)
In-Reply-To: <20081001160827.GA13102@linux-mips.org>
On Wed, 2008-10-01 at 17:08 +0100, Ralf Baechle wrote:
> Doesn't look like it; all invocations of SET_PERSONALITY are passing 0 for
> the ibcs2 argument. So I think the 2nd argument should go entirely. MIPS
> segment against linux-next is below. As you may notice it's actually a
> bug fix, there was a missing else statement that didn't bite bite anybody
> thanks to the unusedness :-)
Hmpf, yes, it is the second argument..
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2008-10-01 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 8:45 RFC: remove ibcs2/PER_SVR4? Martin Schwidefsky
2008-10-01 16:08 ` Ralf Baechle
2008-10-01 16:17 ` Martin Schwidefsky [this message]
2008-10-03 20:21 ` Martin Schwidefsky
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=1222877861.32562.14.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).