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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BA9C8C71153 for ; Tue, 29 Aug 2023 13:28:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235063AbjH2N2Q (ORCPT ); Tue, 29 Aug 2023 09:28:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47498 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236138AbjH2N17 (ORCPT ); Tue, 29 Aug 2023 09:27:59 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AE1CD1BF; Tue, 29 Aug 2023 06:27:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1693315676; x=1724851676; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=laQRomop/n4nHuaCgZ5NZ9HZ/MzLLf0xrWo3cv6IzIE=; b=WMOBye1KLzqHUs2GNLhtirkKGpD/DyAdrLyHh5+cZ/v2lXtdKYMT3eeU FkS+MWv7BbXaStdrwTWL4IfY0ojTCxHl2QUBDeIf7eN6aPKSIxL8MHNnz epB7N7kB4VNpyBYGQCCAXZHkqTGg/1baTzPQM3Ld1omw8XxXhHvreczjD Mz8m/Bh/yCGJSbxQyRg0GJRIvOi0i4BRDzLWtGeFkeIqEjxd60J09XvAC a4iA90Kq6YldIWwqmW0+jShXwNruY4+BvRRQLvs+qsFNEd5JdB7Pg3+Qn itrbUvxKd8JUmeSMvRFH/9yvBXAhDPj2+m3/1cemZAkmN1Vt+kDQ4snnR g==; X-IronPort-AV: E=McAfee;i="6600,9927,10817"; a="354879049" X-IronPort-AV: E=Sophos;i="6.02,210,1688454000"; d="scan'208";a="354879049" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Aug 2023 06:27:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10817"; a="768074772" X-IronPort-AV: E=Sophos;i="6.02,210,1688454000"; d="scan'208";a="768074772" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga008.jf.intel.com with ESMTP; 29 Aug 2023 06:27:01 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1qaykF-004tC2-0a; Tue, 29 Aug 2023 16:26:59 +0300 Date: Tue, 29 Aug 2023 16:26:58 +0300 From: Andy Shevchenko To: Jakub Kicinski Cc: haozhe chang , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Loic Poulain , Sergey Ryazanov , Johannes Berg , "David S. Miller" , Eric Dumazet , Paolo Abeni Subject: Re: [PATCH net-next v1 1/1] wwan: core: Use the bitmap API to allocate bitmaps Message-ID: References: <20230828131953.3721392-1-andriy.shevchenko@linux.intel.com> <20230828124524.5ca4da50@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230828124524.5ca4da50@kernel.org> 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, Aug 28, 2023 at 12:45:24PM -0700, Jakub Kicinski wrote: > On Mon, 28 Aug 2023 16:19:53 +0300 Andy Shevchenko wrote: > > Use bitmap_zalloc() and bitmap_free() instead of hand-writing them. > > It is less verbose and it improves the type checking and semantic. > > > > While at it, add missing header inclusion (should be bitops.h, > > but with the above change it becomes bitmap.h). > > ## Form letter - net-next-closed > > The merge window for v6.6 has begun and therefore net-next is closed > for new drivers, features, code refactoring and optimizations. > We are currently accepting bug fixes only. Sure. > Please repost when net-next reopens after Sept 11th. I'm wondering since we have established lore archive along with `b4` or any analogous tool (since there is an API) why I need to repost. It increases the SNR in the mailing lists, consumes more resources —> adds into global climate change. -- With Best Regards, Andy Shevchenko