All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-rc1 broke OSF binaries on alpha
Date: Sun, 30 Jun 2002 02:45:10 +0400	[thread overview]
Message-ID: <20020630024510.A725@localhost.park.msu.ru> (raw)
In-Reply-To: <E17O7wJ-0007vj-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Jun 29, 2002 at 03:26:18AM +0100

On Sat, Jun 29, 2002 at 03:26:18AM +0100, Alan Cox wrote:
> Please fix the Alpha port. The behaviour fixed is _required_ by SuS.

No objections, but
a) it wasn't a bugfix (just a compliance crap)
b) it seriously broke the alpha port right before the new
   kernel release.

> Make your own alpha syscall that handles this crap.

I'd be happy to see that patch included in 2.4.20-pre1.

Ivan.

  reply	other threads:[~2002-06-29 22:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28 10:54 2.4.19-rc1 broke OSF binaries on alpha Ivan Kokshaysky
2002-06-28 20:31 ` Marcelo Tosatti
2002-06-29  2:28   ` Alan Cox
2002-06-29 23:50     ` Ivan Kokshaysky
2002-07-01  7:54       ` Kurt Garloff
2002-07-01 16:17         ` Jeff Garzik
2002-07-01 13:03       ` jlnance
2002-07-01 14:02         ` Ivan Kokshaysky
2002-07-01 19:40           ` Måns Rullgård
2002-07-02 15:05             ` Ivan Kokshaysky
2002-07-02 23:13               ` Richard Henderson
2002-07-03  0:31                 ` Ivan Kokshaysky
2002-06-29  2:26 ` Alan Cox
2002-06-29 22:45   ` Ivan Kokshaysky [this message]
2002-07-02 20:56     ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2002-06-29  4:39 Chris Adams

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=20020630024510.A725@localhost.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.