From: Paul Fulghum <paulkf@microgate.com>
To: "Butler, Gerald" <GButler@jewels.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: HELP! Slip Interface losing packets. Looking for contractor to fix.
Date: Tue, 13 Jun 2006 11:32:19 -0500 [thread overview]
Message-ID: <448EE893.7040207@microgate.com> (raw)
In-Reply-To: <7697221D47CA0545961FA7846257369103A860C8@ex01.jewels.local>
Butler, Gerald wrote:
> ... a custom compiled Linux Kernel running oh RHEL 3.1
If you post more details (precise description
of hardware setup, problem, and
method of reproducing) you might get a patch for free.
--
Paul Fulghum
Microgate Systems, Ltd.
next prev parent reply other threads:[~2006-06-13 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 15:48 HELP! Slip Interface losing packets. Looking for contractor to fix Butler, Gerald
2006-06-13 16:32 ` Paul Fulghum [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 15:22 Butler, Gerald
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=448EE893.7040207@microgate.com \
--to=paulkf@microgate.com \
--cc=GButler@jewels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).