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 C5314E7849A for ; Mon, 2 Oct 2023 09:39:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236161AbjJBJjl (ORCPT ); Mon, 2 Oct 2023 05:39:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57234 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231164AbjJBJji (ORCPT ); Mon, 2 Oct 2023 05:39:38 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7A117DA; Mon, 2 Oct 2023 02:39:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1696239576; x=1727775576; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=fHrjvcJ6gy9Fptsh53LE767saMnzrLZN5aVBlrefQ7I=; b=Oyg/dXKmKF4r+rnKdvg8K8W/D5S0VJ41xoRyn2Ho0d7M5abtvVaoHOgw a7NbTyLY+e22P9sOTjdtJlb3XLN1B09EGvcpAr9L4FxFhTcXPp5WQ/ySV W3wNBUf6F1x8pQRgxMnjiTtzzADZ04khx7N3qJ8yiXUHiy+ekrwynBkIo rBofcqb9/zPJBNWXGJKKyT8AC0935jUXrqf9DxEN9jpRfCfN+mH02E05y 8zRyc/mKiMqoEST1q4LdurAd5mbK/m0FMYKcPWmq5g8VKdgl8ynDwsPEA PsbjnjrjrOcIr36fo3x9X6GphL3++oZ/5v/6L5mgW6Fm9YDQDbs8js8HO A==; X-IronPort-AV: E=McAfee;i="6600,9927,10850"; a="361988030" X-IronPort-AV: E=Sophos;i="6.03,194,1694761200"; d="scan'208";a="361988030" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Oct 2023 02:39:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10850"; a="997574136" X-IronPort-AV: E=Sophos;i="6.03,194,1694761200"; d="scan'208";a="997574136" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga006.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Oct 2023 02:39:34 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.97-RC0) (envelope-from ) id 1qnFOl-000000027be-1Mac; Mon, 02 Oct 2023 12:39:31 +0300 Date: Mon, 2 Oct 2023 12:39:31 +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 02/11] gpiolib: add support for scope-based management to gpio_device Message-ID: References: <20230927142931.19798-1-brgl@bgdev.pl> <20230927142931.19798-3-brgl@bgdev.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230927142931.19798-3-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:22PM +0200, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > As the few users that need to get the reference to the GPIO device often > release it right after inspecting its properties, let's add support for > the automatic reference release to struct gpio_device. Reviewed-by: Andy Shevchenko -- With Best Regards, Andy Shevchenko