[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFybA=MxezoSCN8ZtbyKdUzto3u+gOJw04w5tWQbYD-1KA@mail.gmail.com>
Date: Mon, 2 Nov 2015 15:21:48 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc: Andy Lutomirski <luto@...capital.net>,
Andy Lutomirski <luto@...nel.org>,
David Miller <davem@...emloft.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Network Development <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT] Networking
On Mon, Nov 2, 2015 at 2:14 PM, Hannes Frederic Sowa
<hannes@...essinduktion.org> 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
--
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
Powered by blists - more mailing lists