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 31D9CC433F5 for ; Wed, 2 Mar 2022 15:51:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235292AbiCBPvz (ORCPT ); Wed, 2 Mar 2022 10:51:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58554 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236478AbiCBPvw (ORCPT ); Wed, 2 Mar 2022 10:51:52 -0500 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0BB78CCC54; Wed, 2 Mar 2022 07:50:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1646236252; x=1677772252; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=D1uiCJhxBtjA4oR6+KrFSQrnollkmcJKddeu5cuEKpA=; b=fo+AMXorGWqlxpuUdk7argusDkRoI7GN9g0+Wye9eLm/VgpLaVn3dG0S xd4BAkLamXwv93XdKXTQ3G8yoBP5aOhZyzLmlBh/s6AK1eFp/4rlWWoUS ey6UMe5FuyXDy4WnIk7fCPNhly9hZqWQ4F6dVRn6kJy/eJagrNjgpnY+q NxitRwwLAUmk8rkcOskpTKAy0UY1ls+R5scJz1R9TsWTM5IvzJ8uqZDXp 1goMlZM3oaRK3Dmr4qKdEpo3Dz/LRlSJCnT21Uh7BQk8RDEwbO97R5BMm ydhcDalPOiBON853oOmHHj/AqAGccD0k5K3tj6Sb+62lzDjFTN7BVRaFr Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10274"; a="234048577" X-IronPort-AV: E=Sophos;i="5.90,149,1643702400"; d="scan'208";a="234048577" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Mar 2022 07:50:40 -0800 X-IronPort-AV: E=Sophos;i="5.90,149,1643702400"; d="scan'208";a="709553789" Received: from smile.fi.intel.com ([10.237.72.59]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Mar 2022 07:50:37 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nPREc-00AMq2-Dc; Wed, 02 Mar 2022 17:49:50 +0200 Date: Wed, 2 Mar 2022 17:49:50 +0200 From: Andy Shevchenko To: "Rafael J. Wysocki" , Hui Wang , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, nvdimm@lists.linux.dev Cc: "Rafael J. Wysocki" , Len Brown , Dan Williams , Vishal Verma , Dave Jiang , Ira Weiny Subject: Re: [PATCH v1 1/1] ACPI: Switch to use list_entry_is_head() helper Message-ID: References: <20220211110423.22733-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220211110423.22733-1-andriy.shevchenko@linux.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Fri, Feb 11, 2022 at 01:04:23PM +0200, Andy Shevchenko wrote: > Since we got list_entry_is_head() helper in the generic header, > we may switch the ACPI modules to use it. This eliminates the > need in additional variable. In some cases it reduces critical > sections as well. Besides the work required in a couple of cases (LKP) there is an ongoing discussion about list loops (and this particular API). Rafael, what do you think is the best course of action here? -- With Best Regards, Andy Shevchenko