linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: "Iain Sandoe" <iain@sandoe.co.uk>
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: network stack oops 2.4.1/gcc 2.95.3
Date: Mon, 29 Jan 2001 14:18:24 -0500	[thread overview]
Message-ID: <200101291918.OAA28870@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from "Iain Sandoe" <iain@sandoe.co.uk> of "Mon, 29 Jan 2001 19:12:36 GMT." <20010129191225.AB75C2EFD2@apollo.valhalla.net>


>>>>> "Iain Sandoe" writes:

Iain> It is not a regression test.  It would not be particularly easy, either to
Iain> put 2.95.2 back up and wind back the system to the build conditions...

Iain> but the version used was 2.95.3-test2. and the bk pull was 2.4.1-pre10.

	A regression is different from a regression test.  I never called
it a regression test.

	I do not mean rewinding all of the way to gcc-2.95.2, but to
Franz's patched version of GCC prior to the gcc-2.95.3 changes.

	I am just trying to narrow down whether this is something new.

David

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

  reply	other threads:[~2001-01-29 19:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 19:12 network stack oops 2.4.1/gcc 2.95.3 Iain Sandoe
2001-01-29 19:18 ` David Edelsohn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-01  0:53 Iain Sandoe
2001-01-30 15:45 Iain Sandoe
2001-01-29 23:54 Iain Sandoe
2001-01-30 12:39 ` Franz Sirl
2001-01-30 17:52   ` David Edelsohn
2001-01-29 19:05 David Edelsohn
2001-01-27 13:36 Iain Sandoe

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=200101291918.OAA28870@mal-ach.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=iain@sandoe.co.uk \
    --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).