All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problems w/  CONFIG_BLK_DEV_MPC8xx_IDE
Date: Thu, 18 Sep 2003 11:25:43 +0200	[thread overview]
Message-ID: <3F697A17.3090909@imc-berlin.de> (raw)
In-Reply-To: <20030917150845.GB14509@ip68-0-152-218.tc.ph.cox.net>


Tom,

>>>>So which is the BK tree to use:
>>>>linuxppc_2_4_devel or linuxppc-2.4 ???
>
> Aside from possible changes to match upstream subsystem rewrites (such
> as IDE) there hasn't been any changes in linuxppc-2.4 specific to 8xx
> that didn't happen in 2_4_devel.
>
>>http://www.penguinppc.org/dev/kernel.shtml calls linuxppc_2_4_devel the
>>"old PPC development tree" !?
>
> That's correct.  It's becoming more of a pain to maintain or own set of
> trees to track 2.4 when Marcelo uses BK as well.

I suppose we need both trees. Otherwise you would have got rid of one. Right? :o)

Steven


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

  reply	other threads:[~2003-09-18  9:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15  7:40 Problems w/ CONFIG_BLK_DEV_MPC8xx_IDE Steven Scholz
2003-09-15 11:31 ` Steven Scholz
2003-09-15 12:00   ` Hubert Figuiere
2003-09-15 12:29     ` Steven Scholz
2003-09-15 15:16       ` Tom Rini
2003-09-16  8:42         ` Steven Scholz
2003-09-17 15:08           ` Tom Rini
2003-09-18  9:25             ` Steven Scholz [this message]
2003-09-18 18:05               ` Tom Rini

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=3F697A17.3090909@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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 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.