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 CA5BBC4167B for ; Fri, 8 Dec 2023 14:06:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1573899AbjLHOGX (ORCPT ); Fri, 8 Dec 2023 09:06:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40382 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1573881AbjLHOGV (ORCPT ); Fri, 8 Dec 2023 09:06:21 -0500 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B34B6A9; Fri, 8 Dec 2023 06:06:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1702044387; x=1733580387; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=pSB/e/wx1Z8iT7xq+6W0PyzyzGdY+5HEvmD3D79YMRY=; b=UxBTc+G5aEra4TP4XCPBJoUwJXfOwSwHkP23P6XNnsKyX1IW1QqeFKxB Yu1xzKlCJyLkjEvfIfroAGAuRkUyK87hS4BQvVMScAnnI54gwXY1vrvU+ gmoegmF1UL+I3zo7ctRNMG5v4Br2FoB/5ZaphNPcaVOdUITaLNUafg7IT 5eNl/Gh3VM4yYxdyCoFeEreghBMbwGT0xnpndMJrWGp3AGgc4+sxM9PhX 0FUO+TBFHKNPc6VCfG5m/tV4wdTZ0Lk0N8sMIC3GYsBJRENthFXi66+CG 7+HRqQUJyRHN+Jmv55RvftsuRV6Ribp9ANthTN3VP2lAnbNlMLtnp4NwC A==; X-IronPort-AV: E=McAfee;i="6600,9927,10917"; a="398275334" X-IronPort-AV: E=Sophos;i="6.04,261,1695711600"; d="scan'208";a="398275334" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Dec 2023 06:06:27 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10917"; a="895546456" X-IronPort-AV: E=Sophos;i="6.04,261,1695711600"; d="scan'208";a="895546456" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga004.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Dec 2023 06:06:25 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.97) (envelope-from ) id 1rBbUk-000000045rp-36hl; Fri, 08 Dec 2023 16:06:22 +0200 Date: Fri, 8 Dec 2023 16:06:22 +0200 From: Andy Shevchenko To: Bartosz Golaszewski Cc: Linus Walleij , Kent Gibson , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, Bartosz Golaszewski Subject: Re: [PATCH v2 1/2] gpiolib: rename static functions that are called with the lock taken Message-ID: References: <20231208102020.36390-1-brgl@bgdev.pl> <20231208102020.36390-2-brgl@bgdev.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231208102020.36390-2-brgl@bgdev.pl> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 08, 2023 at 11:20:19AM +0100, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Rename two functions that read or modify the global GPIO device list but > don't take the lock themselves (and need to be called with it already > acquired). Use the _unlocked() suffix which seems to be used quite > consistently across the kernel despite there also existing the _locked() > suffix for the same purpose. Okay, Reviewed-by: Andy Shevchenko -- With Best Regards, Andy Shevchenko