linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: toa@pop.agri.ch
Cc: Jack Howarth <howarth@bromo.med.uc.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: bk 2.4-test7 broken
Date: Wed, 16 Aug 2000 09:09:03 +0200	[thread overview]
Message-ID: <399A3E0F.EA9685E9@wanadoo.fr> (raw)
In-Reply-To: 3999BA6D.C7C249B0@pop.agri.ch


Andreas Tobler wrote:
[]
> A previous test on linux-pmac-devel(2.4.0-test5) was successful (until
> to the adaptec...), so I tought the changes got in in bk too. Nop, a
> reminder on a previous mail from Takashi I checked the time.c in
> arch/ppc/kernel. The 'mftb' call is still there..... (which the 601
> doesn't likes/understands)
>
> So I think a merge between linuxcare-devel and bk isn't done up to now...

Just for the record: I compiled and run OK both
- linux-pmac-devel as rsynced right now (version 2.4.0-test6)
- linux-bk-devel as of 3 days ago (version 2.4.0-test5)

For those of you who get up to "freeing kernel memory": Did you see the
patch on the linux-kernel mailing list for fs/exec.c
http://boudicca.tux.org/hypermail/linux-kernel/latest/0266.html?
A similar patch is contained in the latest (test7-pre4) patch from
Linus.

I am now trying to back out the recent changes to softirq&Cie...

--
Martin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-08-16  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-15  3:04 bk 2.4-test7 broken Jack Howarth
2000-08-15 11:28 ` Martin Costabel
2000-08-15 18:20   ` Andreas Tobler
2000-08-15 21:47     ` Andreas Tobler
2000-08-16  7:09       ` Martin Costabel [this message]
2000-08-16 14:51     ` Ani Joshi
2000-08-16 19:46       ` Martin Costabel
2000-08-15 19:28   ` Michel Lanners

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=399A3E0F.EA9685E9@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=howarth@bromo.med.uc.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toa@pop.agri.ch \
    /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).