From: Michael Stone <mstone@mathom•us>
To: Stephen Hemminger <shemminger@osdl•org>
Cc: netdev@vger•kernel.org
Subject: Re: [PATCH] skge: fiber support
Date: Wed, 27 Sep 2006 13:59:02 -0400 [thread overview]
Message-ID: <20060927175900.GC6030@mathom.us> (raw)
In-Reply-To: <20060927103415.21bdccc9@freekitty>
On Wed, Sep 27, 2006 at 10:34:15AM -0700, Stephen Hemminger wrote:
>That's surprising, memory leak? dropped packets?
I'm open to suggestions on debugging it. It seems fairly repeatable
about half an hour after startup.
Mike Stone
next prev parent reply other threads:[~2006-09-27 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 13:18 [PATCH] mark sk98lin driver for removal Michael Stone
2006-08-15 18:03 ` Stephen Hemminger
2006-08-15 18:42 ` Michael Stone
2006-08-17 15:21 ` Michael Stone
2006-09-21 22:39 ` [PATCH] skge: fiber support Stephen Hemminger
2006-09-23 0:16 ` Jeff Garzik
2006-09-24 4:25 ` [PATCH] skge: fiber support (rebased) Stephen Hemminger
2006-09-26 0:04 ` Jeff Garzik
2006-09-26 15:45 ` [PATCH] skge: fiber support Michael Stone
2006-09-27 17:26 ` Michael Stone
2006-09-27 17:34 ` Stephen Hemminger
2006-09-27 17:59 ` Michael Stone [this message]
2006-09-27 18:02 ` Stephen Hemminger
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=20060927175900.GC6030@mathom.us \
--to=mstone@mathom$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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