linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: merge progress
Date: Tue, 11 Oct 2005 22:26:55 +1000	[thread overview]
Message-ID: <17227.44943.714106.911471@cargo.ozlabs.ibm.com> (raw)

I have just pushed out a new pile of commits to the powerpc-merge tree
on kernel.org.  (It may take a little while for them to get mirrored
from master.kernel.org to ftp/rsync.kernel.org.)

The current state is that with ARCH=ppc, the merge tree will build all
the ppc32 configs that build in the stock 2.6.14-rc2 tree, and the
powermac configs run (I haven't boot-tested any of the others).

With ARCH=powerpc, a 32-bit powermac target builds (both UP and SMP)
and runs, and a 64-bit pSeries target builds and runs.  64-bit iSeries
builds but there is some weird bug that Stephen Rothwell and BenH have
been chasing.  I haven't got far enough with the merge to be able to
build a 64-bit powermac target.

With ARCH=ppc64, pSeries, iSeries, powermac and maple all build, and
pSeries and iSeries have been boot-tested.  I think I have broken
BPA/cell because it was using pSeries_smp.c (I think we need to make
cell have its own bpa_smp.c or whatever anyway).

I have about a week's backlog of mail, resulting from being on
vacation last week and from concentrating on pushing the merge along.
Tomorrow I'll hopefully get a chance to look at all the patches people
have sent in the last week. :)

Paul.

             reply	other threads:[~2005-10-11 12:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 12:26 Paul Mackerras [this message]
2005-10-11 12:31 ` merge progress Simon Richter
2005-10-17 11:01   ` Paul Mackerras
2005-10-17 22:19     ` Simon Richter
2005-10-18  7:50       ` Geert Uytterhoeven
2005-10-17 22:39     ` Kumar Gala
2005-10-11 18:54 ` Arnd Bergmann

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=17227.44943.714106.911471@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.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).