mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Schwidefsky" <schwidefsky@de.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: zaitcev@redhat.com
Subject: Re: s390 is totally broken in 2.4.18
Date: Tue, 5 Mar 2002 11:10:37 +0100	[thread overview]
Message-ID: <OF6510BC1D.720C525B-ONC1256B73.003619EE@de.ibm.com> (raw)

Hi,

>Apparently, NOBODY bothered to test 2.4.18-pre*, 2.4.18 final,
>or 2.4.19-pre* on s390. The broken patch went into 2.4.18-pre1
>with a curt changelog:
>
>- S390 merge (IBM)
The patch that was merged in 2.4.18-pre* has been created against
2.4.17-pre7 and it did work. The problem is that not all of the
changes I sent Marcelo have been accepted. One of the patches was
the asm-offsets fix that removes all of the hardcoded offsets from
entry.S. Another patch was accepted that changed the thread
structure and this created the inconsistency.

>Patch attached.
Well your patch halfway fixes one of the problems. Halfway because
not the fp_regs structure has changed its size but the pt_regs
pointer has been removed from the thread structure.
Incidentally I sent an s390 update to Marcelo yesterday and the
minimal fixes including an rwsem.h implementation and the partition
detection fixes are about 2000 lines. Want a copy ?

blue skies,
   Martin

Linux/390 Design & Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: schwidefsky@de.ibm.com



             reply	other threads:[~2002-03-05 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05 10:10 Martin Schwidefsky [this message]
2002-03-05 16:43 ` Pete Zaitcev
  -- strict thread matches above, loose matches on Subject: below --
2002-03-06  9:17 Martin Schwidefsky
2002-03-05  5:23 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=OF6510BC1D.720C525B-ONC1256B73.003619EE@de.ibm.com \
    --to=schwidefsky@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®