All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Wolfgang Grandegger <wolfgang.grandegger@bluewin.ch>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: sporadic kernel panic during boot (MPC8xx, FEC)
Date: Thu, 11 Apr 2002 15:00:50 +0200	[thread overview]
Message-ID: <3CB58902.D307BDF1@imc-berlin.de> (raw)
In-Reply-To: 3CB53ACE.4070603@bluewin.ch


Wolfgang,

> AFAIK, this relase tag applies ony to Linus's part of the tree.
> The PPC part is somehow undefined and might be quite old.
> I usually search "bk changes" for "v2.4.18" and then take a
> change-set shortly afterwards e.g.:
>
>   bk export -r1.900 <path>

Hmm. Yeah. Damn. You're right - of course.
I forgot about this.

Thanks a million!

Steven

BTW cs-1.900 seems not to have this kernal panic problem.

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

  reply	other threads:[~2002-04-11 13:00 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
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 [this message]
  -- 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=3CB58902.D307BDF1@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wolfgang.grandegger@bluewin.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 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.