From: David Miller <davem@davemloft.net>
To: amwang@redhat.com
Cc: bjorn@mork.no, netdev@vger.kernel.org, dlstevens@us.ibm.com,
stephen@networkplumber.org
Subject: Re: [Patch net-next v7 4/6] vxlan: add ipv6 support
Date: Tue, 30 Apr 2013 14:58:30 -0400 (EDT) [thread overview]
Message-ID: <20130430.145830.1069552594749915607.davem@davemloft.net> (raw)
In-Reply-To: <1367314694.3216.25.camel@cr0>
From: Cong Wang <amwang@redhat.com>
Date: Tue, 30 Apr 2013 17:38:14 +0800
> On Tue, 2013-04-30 at 11:17 +0200, Bjørn Mork wrote:
>> There is no need to rush
>> this, and people may get tired of looking at the same shortcomings
>> over
>> and over again.
>
> The sooner it gets merged, the less maintaining pains I have. I have to
> solve many conflicts _every time_ I rebase it on to the latest net-next.
You can't force a feature to be ready, when it isn't. And your
complaints about merge conflicts are falling on deaf ears.
If you're frustrated, it's entirely a self inflicted wound. And I
absolutely will not stop the people doing work that is ready just
because you have this patch series which conflicts, but isn't ready.
You have to understand that if this patch series didn't have so many
shortcomings every single submission, it would have been merged weeks
ago.
But that's not what happened, and therefore you're going to miss this
merge window, and you're going to have to be at peace with that.
net-next is closed, I said it's closed, and I even was nicer than
usual by merging in stuff that came in on the last day.
You have no basis upon which to justify merging vxlan ipv6 support in
this merge window, none.
So the earliest you'll be able to resubmit this feature is about two
weeks from now when I re-open net-next. That gives you plenty of time
to correct all of the bugs and semantic problems, rather than trying
to "rush" it into my tree. Rush is synonymous with buggy and not well
cared for, two things I'd like to avoid.
next prev parent reply other threads:[~2013-04-30 18:58 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
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 [this message]
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=20130430.145830.1069552594749915607.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amwang@redhat.com \
--cc=bjorn@mork.no \
--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).