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 00C4CE784B0 for ; Mon, 2 Oct 2023 09:39:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236145AbjJBJjP (ORCPT ); Mon, 2 Oct 2023 05:39:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52124 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230506AbjJBJjN (ORCPT ); Mon, 2 Oct 2023 05:39:13 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.7]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AFF6D83; Mon, 2 Oct 2023 02:39:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1696239551; x=1727775551; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=/27+h6lJjy43p5hcDbnDy7awTHYeKeY4MUaHc4rnRVo=; b=XYeOwJ6OrnbNdf1BxSAqJyfEL12d/+tX2OG+K0QttfPmHX5OwtCS61L2 jKHKlIpAwbQR3WpPiS3lqug2R1PCLMN+X7vTXtNB4Hs4hIw8IWmfcXwgw UOWw05OOPsJYBiZho1w2jMvygm6MTk7wdMkdnwDAHYf/fpFBqBzzn5Qi7 KVhASdtGAcpnC9VlqgsiJ68jtZElO6B1OuWRJ+2BA/tdSL9faD89ldPOI ENorf9qrXMNU+VSMS8+eGHe6aIumlVtjXgkcvY1UCVAP5R3Oe651ULFNo BuSVoBIYI566GnEfg6eqBQbElG4iFDQAfLmQTDV4gXjaFet1256O1Quyh Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10850"; a="4185514" X-IronPort-AV: E=Sophos;i="6.03,194,1694761200"; d="scan'208";a="4185514" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmvoesa101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Oct 2023 02:39:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10850"; a="924215400" X-IronPort-AV: E=Sophos;i="6.03,194,1694761200"; d="scan'208";a="924215400" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga005.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Oct 2023 02:39:08 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.97-RC0) (envelope-from ) id 1qnFOL-000000027b1-0s9c; Mon, 02 Oct 2023 12:39:05 +0300 Date: Mon, 2 Oct 2023 12:39:04 +0300 From: Andy Shevchenko To: Bartosz Golaszewski Cc: Linus Walleij , Mika Westerberg , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, Bartosz Golaszewski Subject: Re: [PATCH v4 01/11] gpiolib: make gpio_device_get() and gpio_device_put() public Message-ID: References: <20230927142931.19798-1-brgl@bgdev.pl> <20230927142931.19798-2-brgl@bgdev.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230927142931.19798-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 Wed, Sep 27, 2023 at 04:29:21PM +0200, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > In order to start migrating away from accessing struct gpio_chip by > users other than their owners, let's first make the reference management > functions for the opaque struct gpio_device public in the driver.h > header. Reviewed-by: Andy Shevchenko -- With Best Regards, Andy Shevchenko