From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@redhat.com>,
VLAN Mailing List <vlan@Scry.WANfear.com>
Subject: [PATCH] 802.1Q VLAN patch, version 1.5
Date: Mon, 22 Oct 2001 21:38:15 -0700 [thread overview]
Message-ID: <3BD4F437.F47ADB3B@candelatech.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
The latest version of my 802.1Q VLAN patch is available at:
http://www.candelatech.com/~greear/vlan.html
The 2.4 kernel patch is attached. This patch should fix the
multicast-reference leak, a crash bug relating to removing
a VLAN device that had been renamed, and some work towards
making VLANs more transparent to snoopy programs (ie tcpdump).
This patch was made against 2.4.13-pre5... Dave, please
consider this for kernel inclusion.
I welcome any feedback, especially things that will help this
patch get into the kernel...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
[-- Attachment #2: vlan.patch.gz --]
[-- Type: application/x-gzip, Size: 24320 bytes --]
reply other threads:[~2001-10-23 4:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BD4F437.F47ADB3B@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vlan@Scry.WANfear.com \
/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