[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <69031552677833@myt1-e20b74e6250c.qloud-c.yandex.net>
Date: Fri, 15 Mar 2019 22:23:53 +0300
From: Andrey Abramov <st5pub@...dex.ru>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
George Spelvin <lkml@....org>,
Andrew Morton <akpm@...ux-foundation.org>,
Daniel Wagner <daniel.wagner@...mens.com>,
Dave Chinner <dchinner@...hat.com>,
Don Mullis <don.mullis@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: Re: [PATCH 4/5] lib/list_sort: Simplify and remove MAX_LIST_LENGTH_BITS
15.03.2019, 22:06, "Andy Shevchenko" <andriy.shevchenko@...ux.intel.com>:
> It makes harder to read and understand the code. One needs spend deciseconds /
> seconds to catch instead of santiseconds of time.
If it is true for someone (for example, for me it is almost as readable
as a simple size_t), then I agree with Geert who said: "use size_t everywhere".
With Best Regards, Andrey Abramov.
Powered by blists - more mailing lists