mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Dan Chen <crimsun@email.unc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18pre4aa1
Date: 22 Jan 2002 02:43:58 -0500	[thread overview]
Message-ID: <1011685438.17096.610.camel@phantasy> (raw)
In-Reply-To: <20020122073742.GA767@opeth.ath.cx>
In-Reply-To: <20020122074806.A1547@athlon.random> <1011682739.17096.563.camel@phantasy>  <20020122073742.GA767@opeth.ath.cx>

On Tue, 2002-01-22 at 02:37, Dan Chen wrote:
> No weird anomalies here. I believe the ones you refer to were a result
> of ipv6 bits not being updated as well. Russell posted two patches for
> those.
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=101164602428323&w=2
> http://marc.theaimsgroup.com/?l=linux-kernel&m=101164602428401&w=2

Maybe, although I seem to recall odd ICMP behavior being the problem. 
Although I don't think the above is in -aa.  Andrea, perhaps this too
should be merged?

Ideally this will all show up in 2.4-proper soon, anyhow.

	Robert Love


  parent reply	other threads:[~2002-01-22  7:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22  6:48 2.4.18pre4aa1 Andrea Arcangeli
2002-01-22  6:58 ` 2.4.18pre4aa1 Robert Love
2002-01-22  7:37   ` 2.4.18pre4aa1 Dan Chen
2002-01-22 10:02     ` 2.4.18pre4aa1 Russell King
2002-01-22 10:12     ` 2.4.18pre4aa1 Robert Love
2002-01-22  7:43   ` Robert Love [this message]
2002-01-24  5:23 2.4.18pre4aa1 rwhron
2002-01-24  6:27 ` 2.4.18pre4aa1 Daniel Phillips
2002-01-25  0:09   ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-28  9:53     ` 2.4.18pre4aa1 Daniel Phillips
2002-01-28 15:29       ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-28 20:28         ` 2.4.18pre4aa1 Daniel Phillips
2002-01-28 23:40           ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-29  0:15             ` 2.4.18pre4aa1 Daniel Phillips
2002-01-29 13:05               ` 2.4.18pre4aa1 Pavel Machek
2002-01-25  0:19   ` 2.4.18pre4aa1 rwhron
2002-01-25  0:29     ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  3:23       ` 2.4.18pre4aa1 rwhron
2002-01-25  3:35         ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  4:56           ` 2.4.18pre4aa1 rwhron
2002-01-25  4:57             ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  5:18               ` 2.4.18pre4aa1 David Weinehall
2002-01-25 17:03                 ` 2.4.18pre4aa1 Rik van Riel
2002-01-25 17:29                   ` 2.4.18pre4aa1 Dave Jones
2002-01-25 12:26           ` 2.4.18pre4aa1 Dave Jones
2002-01-25 14:57             ` 2.4.18pre4aa1 rwhron
2002-01-28  0:37         ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-25  0:11 ` 2.4.18pre4aa1 Andrea Arcangeli

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=1011685438.17096.610.camel@phantasy \
    --to=rml@tech9.net \
    --cc=crimsun@email.unc.edu \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®