From: Cong Wang <amwang@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: netdev@vger.kernel.org, David Stevens <dlstevens@us.ibm.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Patch net-next v7 4/6] vxlan: add ipv6 support
Date: Tue, 30 Apr 2013 17:25:56 +0800 [thread overview]
Message-ID: <1367313956.3216.18.camel@cr0> (raw)
In-Reply-To: <87r4hscr7s.fsf@nemi.mork.no>
On Tue, 2013-04-30 at 11:17 +0200, Bjørn Mork wrote:
> Please take your time to clean up your todo-list and *test* the result
> with different runtime and buildtime settings. There is no need to rush
> this, and people may get tired of looking at the same shortcomings over
> and over again.
>
So, why do you expect it is perfect?
It is extremely normal that a new feature is not perfect initially, and
takes more time to make it perfect. If you need a real example, netlink
mmap is exactly one, the initial version merged into net-next even
doesn't compile for some case.
And, why do you want to rely on me to fix them all?
I am *not* at all an expert on IPv6. If this patchset could be merged
early, many other IPv6 expert can help me to fix the rest issues.
next prev parent reply other threads:[~2013-04-30 9:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 8:43 [Patch net-next v7 0/6] vxlan: add ipv6 support Cong Wang
2013-04-30 8:43 ` [Patch net-next v7 1/6] vxlan: defer vxlan init as late as possible Cong Wang
2013-04-30 8:43 ` [Patch net-next v7 2/6] ipv6: export a stub for ipv6_sock_mc_join and ipv6_sock_mc_drop Cong Wang
2013-04-30 8:43 ` [Patch net-next v7 3/6] ipv6: export in6addr_loopback to modules Cong Wang
2013-04-30 8:43 ` [Patch net-next v7 4/6] vxlan: add ipv6 support Cong Wang
2013-04-30 9:17 ` Bjørn Mork
2013-04-30 9:25 ` Cong Wang [this message]
2013-04-30 10:33 ` Bjørn Mork
2013-04-30 19:06 ` David Miller
2013-05-02 8:05 ` Cong Wang
2013-05-02 8:10 ` David Miller
2013-05-02 12:45 ` Bjørn Mork
2013-05-03 3:02 ` Cong Wang
2013-04-30 19:05 ` David Miller
2013-05-02 7:55 ` Cong Wang
2013-04-30 9:38 ` Cong Wang
2013-04-30 18:58 ` David Miller
2013-04-30 19:04 ` David Miller
2013-04-30 8:43 ` [Patch net-next v7 5/6] vxlan: respect disable_ipv6 sysctl Cong Wang
2013-04-30 12:27 ` Sergei Shtylyov
2013-04-30 8:43 ` [Patch net-next v7 6/6] ipv6: Add generic UDP Tunnel segmentation Cong Wang
2013-04-30 19:00 ` [Patch net-next v7 0/6] vxlan: add ipv6 support David Miller
2013-05-02 7:02 ` Cong Wang
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=1367313956.3216.18.camel@cr0 \
--to=amwang@redhat.com \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).