From: Stephen Hemminger <stephen@networkplumber.org>
To: Cong Wang <amwang@redhat.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [Patch net-next v5 0/5] vxlan: add ipv6 support
Date: Mon, 22 Apr 2013 23:51:09 -0700 [thread overview]
Message-ID: <20130422235109.296696a4@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1366698455.21136.11.camel@cr0>
On Tue, 23 Apr 2013 14:27:35 +0800
Cong Wang <amwang@redhat.com> wrote:
> After several tries, I think it is not easy to do at all, it relies on
> some icmp functions at least, which are still compiled as a module. So,
> I can't think out any easier solution than simply adding Kconfig
> dependency.
Why is IPv6 support depending on ICMP functions? Everything doesn't
have to be hyper optimized, at least not initially.
next prev parent reply other threads:[~2013-04-23 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 14:23 [Patch net-next v5 0/5] vxlan: add ipv6 support Cong Wang
2013-04-21 14:23 ` [Patch net-next v5 1/5] vxlan: defer vxlan init as late as possible Cong Wang
2013-04-21 14:23 ` [Patch net-next v5 2/5] ipv6: export ipv6_sock_mc_join and ipv6_sock_mc_drop Cong Wang
2013-04-21 14:23 ` [Patch net-next v5 3/5] ipv6: export in6addr_loopback to modules Cong Wang
2013-04-21 14:23 ` [Patch net-next v5 4/5] vxlan: add ipv6 support Cong Wang
2013-04-22 12:43 ` David Stevens
2013-04-21 14:23 ` [Patch net-next v5 5/5] ipv6: Add generic UDP Tunnel segmentation Cong Wang
2013-04-21 19:42 ` [Patch net-next v5 0/5] vxlan: add ipv6 support Stephen Hemminger
2013-04-22 20:08 ` David Miller
2013-04-23 3:30 ` Cong Wang
2013-04-23 6:27 ` Cong Wang
2013-04-23 6:51 ` Stephen Hemminger [this message]
2013-04-23 6:59 ` Cong Wang
2013-04-23 7:05 ` David Miller
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=20130422235109.296696a4@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@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 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.