From: Paul Fulghum <paulkf@microgate.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] syncppp broken - how to fix?
Date: 03 Mar 2004 14:16:24 -0600 [thread overview]
Message-ID: <1078344984.2118.43.camel@deimos.microgate.com> (raw)
In-Reply-To: <20040303114906.1a4027da@dell_ss3.pdx.osdl.net>
On Wed, 2004-03-03 at 13:49, Stephen Hemminger wrote:
> That assert can go, it is a left over from the conversion
> of the wan devices to use alloc_netdev.
OK
> The whole ppp structure layering
> is a mess; with a bad case of assumed encapsulation.
Agreed, it is *really* ugly.
I've decided to alter the synclink drivers to
work with and without the new assertion. That
way, our customers can download updated
drivers from our web site which will work
with any 2.6 kernel.
Removing the assertion fixes things for the
other drivers starting with kernel 2.6.5
--
Paul Fulghum
paulkf@microgate.com
prev parent reply other threads:[~2004-03-03 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 19:19 [RFC] syncppp broken - how to fix? Paul Fulghum
[not found] ` <1078341865.2118.22.camel@deimos.microgate.com>
[not found] ` <20040303114906.1a4027da@dell_ss3.pdx.osdl.net>
2004-03-03 20:16 ` Paul Fulghum [this message]
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=1078344984.2118.43.camel@deimos.microgate.com \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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