From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6E852C11F68 for ; Tue, 29 Jun 2021 16:18:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5659861DE3 for ; Tue, 29 Jun 2021 16:18:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232574AbhF2QVU (ORCPT ); Tue, 29 Jun 2021 12:21:20 -0400 Received: from mga17.intel.com ([192.55.52.151]:31956 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232355AbhF2QVN (ORCPT ); Tue, 29 Jun 2021 12:21:13 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10030"; a="188559933" X-IronPort-AV: E=Sophos;i="5.83,309,1616482800"; d="scan'208";a="188559933" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jun 2021 09:18:31 -0700 X-IronPort-AV: E=Sophos;i="5.83,309,1616482800"; d="scan'208";a="489305510" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.40]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jun 2021 09:18:25 -0700 Received: from andy by smile with local (Exim 4.94.2) (envelope-from ) id 1lyGRH-006Ktj-7b; Tue, 29 Jun 2021 19:18:19 +0300 Date: Tue, 29 Jun 2021 19:18:19 +0300 From: Andy Shevchenko To: Yury Norov Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Benjamin Herrenschmidt , Catalin Marinas , Will Deacon , Yoshinori Sato , Brian Cain , Geert Uytterhoeven , Thomas Bogendoerfer , Jonas Bonn , Stefan Kristiansson , "James E.J. Bottomley" , Palmer Dabbelt , Heiko Carstens , Rich Felker , David Hildenbrand , Jaegeuk Kim , Arnd Bergmann , Rasmus Villemoes , Andrew Morton , Alexander Lobakin , Samuel Mendoza-Jonas , Jakub Kicinski , Daniel Bristot de Oliveira , Alexey Klimov , Ingo Molnar Subject: Re: [PATCH 0/8] all: use find_next_*_bit() instead of find_first_*_bit() where possible Message-ID: References: <20210612123639.329047-1-yury.norov@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 28, 2021 at 06:48:20PM -0700, Yury Norov wrote: > On Sat, Jun 12, 2021 at 05:36:31AM -0700, Yury Norov wrote: > > find_first_*_bit() is simpler and faster than 'next' version [1], and they > > work identically if start == 0. But in many cases kernel code uses the > > 'next' version where 'first' can be used. This series addresses this issue. > > > > Patches 1-3 move find.h under include/linux as it simplifies development. > > Patches 4-8 switch the kernel and tools to find_first_*_bit() implementation > > where appropriate. > > Guys, do we have any blocker for this series? If not, I'd like to have it > merged in this window. > > And this too: https://lore.kernel.org/lkml/YNirnaYw1GSxg1jK@yury-ThinkPad/T/ "This window" now equals for v5.15-rc1, hence we have a few weeks time anyway. -- With Best Regards, Andy Shevchenko