From: Adrian Bunk <bunk@stusta.de>
To: chas3@users.sourceforge.net
Cc: netdev@oss.sgi.com, linux-atm-general@lists.sourceforge.net,
bridge@osdl.org, linux-kernel@vger.kernel.org,
shemminger@osdl.org
Subject: [Bridge] Re: [2.6 patch] fix bridge <-> ATM compile error
Date: Wed, 16 Mar 2005 19:15:32 +0100 [thread overview]
Message-ID: <20050316181532.GA3251@stusta.de> (raw)
In-Reply-To: <200503161611.j2GGBT0F004479@ginger.cmf.nrl.navy.mil>
On Wed, Mar 16, 2005 at 11:11:29AM -0500, chas williams - CONTRACTOR wrote:
> In message <20050315121930.GE3189@stusta.de>,Adrian Bunk writes:
> >This patch fixes the following compile error with CONFIG_BRIDGE=y and
> >CONFIG_ATM_LANE=m:
>
> isnt the problem more that CONFIG_ATM=m not CONFIG_ATM_LANE=m?
> perhaps CONFIG_BRIDGE should be dependent on CONFIG_ATM. if
> atm is a module then bridge cannot be a module (unless the
> hooks are moved from atm to bridge)?
The problem is currently CONFIG_ATM_LANE due to the #ifdef's in
net/atm/common.c .
Letting CONFIG_BRIDGE depend on CONFIG_ATM doesn't sound like a good
idea, since I doubt all people using the Bridge code require ATM
support.
Moving the hooks to the bridge code will give you exactly the same
problems the other way round.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: chas3@users.sourceforge.net
Cc: shemminger@osdl.org, bridge@osdl.org,
linux-atm-general@lists.sourceforge.net, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] fix bridge <-> ATM compile error
Date: Wed, 16 Mar 2005 19:15:32 +0100 [thread overview]
Message-ID: <20050316181532.GA3251@stusta.de> (raw)
In-Reply-To: <200503161611.j2GGBT0F004479@ginger.cmf.nrl.navy.mil>
On Wed, Mar 16, 2005 at 11:11:29AM -0500, chas williams - CONTRACTOR wrote:
> In message <20050315121930.GE3189@stusta.de>,Adrian Bunk writes:
> >This patch fixes the following compile error with CONFIG_BRIDGE=y and
> >CONFIG_ATM_LANE=m:
>
> isnt the problem more that CONFIG_ATM=m not CONFIG_ATM_LANE=m?
> perhaps CONFIG_BRIDGE should be dependent on CONFIG_ATM. if
> atm is a module then bridge cannot be a module (unless the
> hooks are moved from atm to bridge)?
The problem is currently CONFIG_ATM_LANE due to the #ifdef's in
net/atm/common.c .
Letting CONFIG_BRIDGE depend on CONFIG_ATM doesn't sound like a good
idea, since I doubt all people using the Bridge code require ATM
support.
Moving the hooks to the bridge code will give you exactly the same
problems the other way round.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-03-16 18:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 12:19 [Bridge] [2.6 patch] fix bridge <-> ATM compile error Adrian Bunk
2005-03-15 12:19 ` Adrian Bunk
2005-03-15 17:13 ` [Bridge] " Stephen Hemminger
2005-03-15 17:13 ` Stephen Hemminger
2005-03-15 17:25 ` Adrian Bunk
2005-03-15 17:25 ` [Bridge] " Adrian Bunk
2005-03-15 17:25 ` Adrian Bunk
2005-03-16 16:11 ` [Bridge] " chas williams - CONTRACTOR
2005-03-16 16:11 ` chas williams - CONTRACTOR
2005-03-16 18:15 ` Adrian Bunk [this message]
2005-03-16 18:15 ` Adrian Bunk
2005-03-16 18:24 ` [Bridge] " chas williams - CONTRACTOR
2005-03-16 18:24 ` chas williams - CONTRACTOR
2005-03-17 20:36 ` [Bridge] " chas williams - CONTRACTOR
2005-03-17 20:36 ` chas williams - CONTRACTOR
2005-03-19 23:04 ` [Bridge] " Adrian Bunk
2005-03-19 23:04 ` Adrian Bunk
2005-03-28 19:11 ` [Bridge] " Stephen Hemminger
2005-03-28 19:11 ` 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=20050316181532.GA3251@stusta.de \
--to=bunk@stusta.de \
--cc=bridge@osdl.org \
--cc=chas3@users.sourceforge.net \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--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 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.