All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: sporadic kernel panic during boot (MPC8xx, FEC)
Date: Fri, 12 Apr 2002 08:25:09 -0700	[thread overview]
Message-ID: <20020412152509.GQ759@opus.bloom.county> (raw)
In-Reply-To: <3CB6F9B7.16378395@imc-berlin.de>


On Fri, Apr 12, 2002 at 05:13:59PM +0200, Steven Scholz wrote:
>
> Tom Rini wrote:
>
> > > Define stable :-(
> > Well, whichever ChangeSet is the merge of someplace:/.../linux_2_4 into
> > someplace:/.../linuxppc_2_4 is the merge into linuxppc_2_4.
>
> ??? Excuse me? :-(
> What did you say?

Well, in the linuxppc_2_4 and linuxppc_2_4_devel trees (this doesn't
hold true for the Linus and Marcelo BK trees since they work differently):
ChangeSet@1.604, 2002-04-05 10:17:36-07:00, trini@opus.bloom.county
  Merge opus.bloom.county:/home/trini/work/kernel/pristine/linux_2_4
  into opus.bloom.county:/home/trini/work/kernel/pristine/linuxppc_2_4

ChangeSet@1.2.2.138, 2002-04-05 10:11:39-07:00, trini@opus.bloom.county
  patch-2.4.19-pre5-pre6
  TAG: v2.4.19-pre6


So 1.604 will get you 2.4.19-pre6 in the linuxppc_2_4 tree.

In the linuxppc_2_4_devel tree:
ChangeSet@1.900, 2002-02-26 17:37:17-07:00, trini@opus.bloom.county
  Merge opus.bloom.county:/home/trini/work/kernel/pristine/linuxppc_2_4
  into opus.bloom.county:/home/trini/work/kernel/pristine/linuxppc_2_4_devel

ChangeSet@1.118.1.473, 2002-02-26 17:31:25-07:00, trini@opus.bloom.county
  Merge opus.bloom.county:/home/trini/work/kernel/pristine/linux_2_4
  into opus.bloom.county:/home/trini/work/kernel/pristine/linuxppc_2_4

ChangeSet@1.2.2.133, 2002-02-26 17:28:14-07:00, trini@opus.bloom.county
  The actual change in 2.4.18-rc4 got applied twice, revert.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

  reply	other threads:[~2002-04-12 15:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11  7:07 sporadic kernel panic during boot (MPC8xx, FEC) Steven Scholz
2002-04-11  7:18 ` Christian Pellegrin
2002-04-11  7:23   ` Steven Scholz
2002-04-11  7:27     ` Christian Pellegrin
2002-04-11 15:31     ` Tom Rini
2002-04-11 15:41       ` Steven Scholz
2002-04-11 19:06       ` Wolfgang Grandegger
2002-04-11 19:12         ` Tom Rini
2002-04-12  9:03           ` Steven Scholz
2002-04-12 13:33             ` Wolfgang Denk
2002-04-12 15:08               ` Tom Rini
2002-04-12 15:13                 ` Steven Scholz
2002-04-12 15:25                   ` Tom Rini [this message]
2002-04-12 15:25                 ` Wolfgang Denk
2002-04-12 17:13                   ` Tom Rini
2002-04-11  7:27 ` Wolfgang Grandegger
2002-04-11 13:00   ` Steven Scholz
  -- strict thread matches above, loose matches on Subject: below --
2002-04-11 10:00 Kári Davíðsson
2002-04-11 13:03 ` Steven Scholz

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=20020412152509.GQ759@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.de \
    /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.