From: Adrian Bunk <bunk@stusta.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
dtor_core@ameritech.net, jgeorgas@rogers.com,
linux-kernel@vger.kernel.org
Subject: Re: make IPV4 modular (was: [2.6 patch] make UNIX a bool)
Date: Fri, 3 Mar 2006 14:52:03 +0100 [thread overview]
Message-ID: <20060303135202.GP9295@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0603031430280.2581@yvahk01.tjqt.qr>
On Fri, Mar 03, 2006 at 02:31:04PM +0100, Jan Engelhardt wrote:
> >> Well, not directly topic'ed to CONFIG_UNIX, but if the IPv4 stack was modular
> >> (like IPv6), we'd probably gain some 100 KB and would not have to worry about
> >> CONFIG_UNIX for a while.
> >
> >I doubt making the IPv4 stack modular is worth the trouble, but feel
> >free to send a patch as a basis for a discussion...
> >
> It would possibly require EXPORT_SYMBOLs, which you seem to be opposed to...
That's not the only point.
There are many cases you have to handle correctly. As a simple example,
CONFIG_W1=y, CONFIG_NET=m or CONFIG_W1=m, CONFIG_NET=m should compile as
expected.
But hey, it's open source and much is possible. If you think this would
be important send a patch and we have a basis for a discussion.
Discussions about probable patches tend to become extremely fruitless.
> Jan Engelhardt
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:[~2006-03-03 13:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 16:01 [2.6 patch] make UNIX a bool Adrian Bunk
2006-02-25 17:13 ` Stephen Hemminger
2006-02-25 17:28 ` Arjan van de Ven
2006-02-26 18:19 ` Diego Calleja
2006-02-25 22:46 ` Olaf Hering
2006-03-25 19:47 ` Adrian Bunk
2006-03-26 15:20 ` Jan-Benedict Glaw
2006-03-26 21:48 ` Joshua Hudson
2006-02-27 22:18 ` James C. Georgas
2006-02-27 22:29 ` Adrian Bunk
2006-03-01 3:09 ` Dmitry Torokhov
2006-03-01 17:58 ` Adrian Bunk
2006-03-02 1:31 ` Herbert Xu
2006-03-02 17:38 ` Adrian Bunk
2006-03-02 19:51 ` Jan-Benedict Glaw
2006-03-02 20:39 ` Adrian Bunk
2006-03-02 20:51 ` Jan-Benedict Glaw
2006-03-02 21:28 ` Adrian Bunk
2006-03-03 9:27 ` Jan-Benedict Glaw
2006-03-02 20:28 ` Jesper Juhl
2006-03-02 20:32 ` Adrian Bunk
2006-03-02 20:40 ` Jesper Juhl
2006-03-02 21:40 ` Adrian Bunk
2006-03-02 21:53 ` Jan Engelhardt
2006-03-02 22:32 ` Adrian Bunk
2006-03-03 13:31 ` make IPV4 modular (was: [2.6 patch] make UNIX a bool) Jan Engelhardt
2006-03-03 13:52 ` Adrian Bunk [this message]
2006-03-02 21:46 ` [2.6 patch] make UNIX a bool Adrian Bunk
2006-03-03 9:30 ` Jan-Benedict Glaw
2006-03-03 4:28 ` James C. Georgas
[not found] ` <1141335521.3582.14.camel@Rainsong.home>
[not found] ` <20060302214423.GI9295@stusta.de>
2006-03-03 4:44 ` James C. Georgas
2006-03-03 11:46 ` Adrian Bunk
2006-03-03 14:48 ` James C. Georgas
2006-03-03 15:10 ` Adrian Bunk
2006-03-03 17:50 ` James C. Georgas
2006-03-03 17:55 ` Adrian Bunk
2006-03-03 21:11 ` James C. Georgas
2006-03-02 20:34 ` Randy.Dunlap
2006-02-28 14:52 ` Jan-Benedict Glaw
2006-02-28 15:30 ` James C. Georgas
2006-02-28 19:15 ` Jan Engelhardt
2006-03-02 21:47 ` Adrian Bunk
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=20060303135202.GP9295@stusta.de \
--to=bunk@stusta.de \
--cc=dtor_core@ameritech.net \
--cc=herbert@gondor.apana.org.au \
--cc=jengelh@linux01.gwdg.de \
--cc=jesper.juhl@gmail.com \
--cc=jgeorgas@rogers.com \
--cc=linux-kernel@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
Powered by JetHome