From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932290AbdJYP26 (ORCPT ); Wed, 25 Oct 2017 11:28:58 -0400 Received: from mail-wm0-f46.google.com ([74.125.82.46]:51488 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932270AbdJYP2z (ORCPT ); Wed, 25 Oct 2017 11:28:55 -0400 X-Google-Smtp-Source: ABhQp+QulAy3L/xYK3qasVAKbeDtERGSBG+VfTB3JfXBwqeDcYgpnGypqSojmjLdJyWFjmzCpDN1yw== From: Clement Courbet To: Arnd Bergmann , Rasmus Villemoes , Andrew Morton , Matthew Wilcox , Yury Norov Cc: Clement Courbet , Ingo Molnar , linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re [PATCH v2] lib: optimize cpumask_next_and() Date: Wed, 25 Oct 2017 17:28:41 +0200 Message-Id: <20171025152841.6746-1-courbet@google.com> X-Mailer: git-send-email 2.15.0.rc2.357.g7e34df9404-goog In-Reply-To: <20171025145938.wpr7spsujounqudk@yury-thinkpad> References: <20171025145938.wpr7spsujounqudk@yury-thinkpad> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks for the comments Yury. > But I'd like also to keep _find_next_bit() consistent with > _find_next_bit_le() Not sure I understand what you're suggesting here: Do you want a find_next_and_bit_le() or do you want to make _find_next_bit_le() more like _find_next_bit() ? In the latter case we might just want to merge it with _find_next_bit() and end up with an extra is_le parameter :)