From: Ben Greear <greearb@candelatech.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org,
VLAN Mailing List <vlan@Scry.WANfear.com>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: [patch] 2.4.16: 802.1Q VLAN non-modular
Date: Mon, 26 Nov 2001 20:37:23 -0700 [thread overview]
Message-ID: <3C030A73.8080506@candelatech.com> (raw)
In-Reply-To: <10181.1006827895@kao2.melbourne.sgi.com>
By the way, I just successfully compiled 2.4.16 (including VLAN
builtin) with no problems. It looks like Maciej is compiling
MIPS, so it may be a bug particular to that platform??
Keith Owens wrote:
> On Mon, 26 Nov 2001 14:35:55 -0200 (BRST),
> Rik van Riel <riel@conectiva.com.br> wrote:
>
>>On Mon, 26 Nov 2001, Maciej W. Rozycki wrote:
>>
>>
>>> It appears the 802.1Q VLAN support didn't receive even basic testing,
>>>sigh... It doesn't compile non-modular, due to vlan_proc_cleanup() being
>>>discarded, yet needed in vlan_proc_init(). Following is a fix.
--
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
next prev parent reply other threads:[~2001-11-27 3:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 16:03 [patch] 2.4.16: 802.1Q VLAN non-modular Maciej W. Rozycki
2001-11-26 16:35 ` Rik van Riel
2001-11-27 2:24 ` Keith Owens
2001-11-27 3:37 ` Ben Greear [this message]
2001-11-27 11:50 ` Maciej W. Rozycki
2001-11-27 9:36 ` Chris Wedgwood
2001-11-27 1:55 ` Ben Greear
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 7:55 willy tarreau
[not found] <fa.ns5og9v.u04srk@ifi.uio.no>
[not found] ` <fa.hfatgnv.q50k9n@ifi.uio.no>
2001-11-27 8:32 ` Giacomo Catenazzi
2001-11-27 8:59 ` Keith Owens
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=3C030A73.8080506@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.