[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwAK9D7Q=7TU0Mqo4eD9Vkkgs0rFq3PLnbg3sd1+9NqCw@mail.gmail.com>
Date: Tue, 25 Jul 2017 08:43:39 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Davidlohr Bueso <dave@...olabs.net>,
Anshul Garg <aksgarg1989@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Will Deacon <will.deacon@....com>,
Joe Perches <joe@...ches.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] lib/int_sqrt: Optimize initial value compute
On Tue, Jul 25, 2017 at 1:17 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Mon, Jul 24, 2017 at 10:35:56AM -0700, Linus Torvalds wrote:
>> Ack. You have numbers, it's all good.
>
> Thanks!
>
>> Except I'd still want you to comment on why you cared and about which
>> piece of your upcoming code this is going to matter for, ok?
>
> I did an RFC here:
>
> https://lkml.kernel.org/r/20170719133940.uytsixvfgpmo3ane@hirez.programming.kicks-ass.net
Christ Peter.
I meant add the explanation to the commit log, to explain *why* you
care about this function that nobody has ever cared about before.
Please. Document your patches. Don't make people ask for explanations.
I've asked now *three* times about this, and still the patch
submission had no explanation at all about why this mattered.
How many times do people have to ask before you start saying "oh,
maybe I should explain why.." in your patch.
Linus
Powered by blists - more mailing lists