From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [GIT] Networking Date: Mon, 2 Nov 2015 15:21:48 -0800 Message-ID: References: <20151027.233235.1641084823622810663.davem@davemloft.net> <5637C8DF.800@kernel.org> <1446502448.296003.427190649.434774F6@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Andy Lutomirski , Andy Lutomirski , David Miller , Andrew Morton , Network Development , Linux Kernel Mailing List To: Hannes Frederic Sowa Return-path: In-Reply-To: <1446502448.296003.427190649.434774F6@webmail.messagingengine.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Mon, Nov 2, 2015 at 2:14 PM, Hannes Frederic Sowa wrote: > > overflow_usub was part of a larger header I already prepared to offer > support for *all* overflow_* checking builtins. While fixing this IPv6 > bug I thought I could hopefully introduce this interface slowly and > simply cut away the other versions. Hell no. Both you and Andy seem to argue that "since there are other totally unrelated functions that look superficially similar and actually some sense, we should add these stupid crap functions too". In exactly *WHAT* crazy universe does that make sense as an argument? It's like saying "I put literal shit on your plate, because there are potentially nutritious sausages that look superficially a bit like the dogshit I served you". Seriously. The fact that _valid_ overflow checking functions exist in _no_ way support the crap that I got. It's *exactly* the same argument as "dog poop superficially looks like good sausages". Is that really your argument? There is never an excuse for "usub_overflow()". It's that simple. No amount of _other_ overflow functions make that shit palatable. Linus