From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: bunk@stusta.de
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org,
yoshfuji@linux-ipv6.org
Subject: Re: [2.6 patch] net/ipv6/: misc cleanups
Date: Fri, 07 Jan 2005 12:11:49 +0900 (JST) [thread overview]
Message-ID: <20050107.121149.102802103.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20050107030017.GF14108@stusta.de>
In article <20050107030017.GF14108@stusta.de> (at Fri, 7 Jan 2005 04:00:17 +0100), Adrian Bunk <bunk@stusta.de> says:
> - #if 0 the following unused global variable:
> - addrconf.c: in6addr_any
> - remove the following EXPORT_SYMBOL's:
> - ipv6_syms.c: in6addr_any
> - ipv6_syms.c: in6addr_loopback
:
> --- linux-2.6.10-mm2-full/include/linux/in6.h.old 2005-01-07 02:34:21.000000000 +0100
> +++ linux-2.6.10-mm2-full/include/linux/in6.h 2005-01-07 02:36:18.000000000 +0100
> @@ -44,10 +44,10 @@
> * NOTE: Be aware the IN6ADDR_* constants and in6addr_* externals are defined
> * in network byte order, not in host byte order as are the IPv4 equivalents
> */
> +#if 0
> extern const struct in6_addr in6addr_any;
> #define IN6ADDR_ANY_INIT { { { 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 } } }
> -extern const struct in6_addr in6addr_loopback;
> -#define IN6ADDR_LOOPBACK_INIT { { { 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1 } } }
> +#endif
>
I meant:
#if 0
extern const struct in6_addr in6addr_any;
#define IN6ADDR_ANY_INIT { { { 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 } } }
#endif
extern const struct in6_addr in6addr_loopback;
#define IN6ADDR_LOOPBACK_INIT { { { 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1 } } }
And,
> @@ -191,7 +188,11 @@
> };
>
> /* IPv6 Wildcard Address and Loopback Address defined by RFC2553 */
> +#if 0
> +#define IN6ADDR_ANY_INIT { { { 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 } } }
> const struct in6_addr in6addr_any = IN6ADDR_ANY_INIT;
> +#endif
> +#define IN6ADDR_LOOPBACK_INIT { { { 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1 } } }
> const struct in6_addr in6addr_loopback = IN6ADDR_LOOPBACK_INIT;
>
#if 0
const struct in6_addr in6addr_any = IN6ADDR_ANY_INIT;
#endif
const struct in6_addr in6addr_loopback = IN6ADDR_LOOPBACK_INIT;
or something like this.
--yoshfuji
next prev parent reply other threads:[~2005-01-07 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 0:55 [2.6 patch] net/ipv6/: misc possible cleanups Adrian Bunk
2004-12-15 1:59 ` YOSHIFUJI Hideaki / 吉藤英明
2005-01-07 3:00 ` [2.6 patch] net/ipv6/: misc cleanups Adrian Bunk
2005-01-07 3:11 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2005-01-08 23:32 ` 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=20050107.121149.102802103.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).