linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: jlquinn@us.ibm.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Building 2.3.35?
Date: Thu, 6 Jan 2000 17:19:19 +0100	[thread overview]
Message-ID: <20000106171919.015242@mailhost.mipsys.com> (raw)
In-Reply-To: <8525685E.0056E2AE.00@D51MTA03.pok.ibm.com>


On Thu, Jan 6, 2000,  <jlquinn@us.ibm.com> wrote:


>2.3.35 is the first unstable kernel that I've put some effort in getting to
>build.  I only get to play with stuff for 2-3 hours a week, so it's hard to
>really do debugging at the rate of kernel development :-)
>
>How does merging of the vger tree into Linus' development kernel work right
>now?

The main ppc tree, for now, is not vger but Cort's bitkeeper. (I don't
know if Cort keeps vger updated).

2.2.x is fully in sync with Linus (except for the USB backport, but
that's normal).
2.3.x changes are, I think, sent to linus regulary, but there is still
some work needed to get the latest 2.3.35/36 kernels to work on powermac.
Hopefully Cort, Paul and I (and probably others are working on this).


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

  reply	other threads:[~2000-01-06 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06 15:49 Building 2.3.35? jlquinn
2000-01-06 16:19 ` Benjamin Herrenschmidt [this message]
2000-01-06 20:17   ` Geert Uytterhoeven
2000-01-06 20:21     ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2000-01-06 15:25 jlquinn
2000-01-06 15:38 ` Andreas Tobler

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=20000106171919.015242@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=jlquinn@us.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.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).