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 possible cleanups
Date: Wed, 15 Dec 2004 10:59:00 +0900 (JST) [thread overview]
Message-ID: <20041215.105900.27736391.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20041215005546.GA11972@stusta.de>
In article <20041215005546.GA11972@stusta.de> (at Wed, 15 Dec 2004 01:55:46 +0100), Adrian Bunk <bunk@stusta.de> says:
> The patch below contains the following possible cleanups:
> - make some needlessly global code static
> - remove the following unused functions:
> - exthdrs.c: ipv6_build_rthdr
> - exthdrs.c: ipv6_build_exthdr
> - exthdrs.c: ipv6_build_nfrag_opts
> - exthdrs.c: ipv6_build_frag_opts
> - remove the following unused global variables:
> - addrconf.c: in6addr_any
> - remove the following EXPORT_SYMBOL's:
> - ipv6_syms.c: addrconf_lock
> - ipv6_syms.c: in6addr_any
> - ipv6_syms.c: in6addr_loopback
>
> Please comment on which of these changes are correct and which conflict
> with pending patches.
Please keep addrconf_lock (for SCTP).
Please keep in6addr_any in addrconf.c (or enclose by #if 0 ... #endif)
> --- linux-2.6.10-rc3-mm1-full/include/net/ip.h.old 2004-12-14 05:20:46.000000000 +0100
> +++ linux-2.6.10-rc3-mm1-full/include/net/ip.h 2004-12-14 05:20:53.000000000 +0100
:
I think you attatched incorrect patch file.
--yoshfuji
next prev parent reply other threads:[~2004-12-15 1:58 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 / 吉藤英明 [this message]
2005-01-07 3:00 ` [2.6 patch] net/ipv6/: misc cleanups Adrian Bunk
2005-01-07 3:11 ` YOSHIFUJI Hideaki / 吉藤英明
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=20041215.105900.27736391.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).