Date: Wed, 6 Sep 2000 14:15:08 +0300 (EEST)
From: "Pekka Riikonen [Adm]" <[EMAIL PROTECTED]>
I think that interface programmers should think
whether their public interfaces might be needed from the modules
and export symbols accordingly.
Yes, but only when actually used.
The ipv4
: I mean show me real code, not hypothetical examples.
:
Like code that I'm doing currently though not ready and not to be
included into the main kernel. The point is that corresponding IPv4
symbols are exported as well why should we restrict IPv6? I bet after
IPv6 is used more commonly the ne
Date: Wed, 6 Sep 2000 13:48:05 +0300 (EEST)
From: "Pekka Riikonen [Adm]" <[EMAIL PROTECTED]>
For example, any module that ...
I mean show me real code, not hypothetical examples.
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-
: What needs access to these ipv6 symbols? Do tell...
:
For example, any module that performs packet manipulation for example in
netfilter hooks using IPv6. Currently such modules might be impossible to
do if they need to for example copy and resend packets (they also might
need to do route loo
What needs access to these ipv6 symbols? Do tell...
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Enclosed is a patch that exports some IPv6 specific symbols on 2.4 so that
finally IPv6 is accessible from modules. I bet there are bunch of other
functions that needs to be exported as well but this is a start. There
are also various IPv6 functions in 2.2 that should be exported for the
same r
6 matches
Mail list logo
