netdev - Re: [Patch net-next v7 4/6] vxlan: add ipv6 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130430.145830.1069552594749915607.davem@davemloft.net>
Date:	Tue, 30 Apr 2013 14:58:30 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	amwang@...hat.com
Cc:	bjorn@...k.no, netdev@...r.kernel.org, dlstevens@...ibm.com,
	stephen@...workplumber.org
Subject: Re: [Patch net-next v7 4/6] vxlan: add ipv6 support

From: Cong Wang <amwang@...hat.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html