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 56F73CCFA0A for ; Wed, 6 Sep 2023 14:50:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241901AbjIFOuQ (ORCPT ); Wed, 6 Sep 2023 10:50:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50098 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229564AbjIFOuP (ORCPT ); Wed, 6 Sep 2023 10:50:15 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 398A810D0; Wed, 6 Sep 2023 07:50:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1694011812; x=1725547812; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=oXdfGzzZdVeNB8WOqcbJ3fq9pHu4f2PCymvo5LTc6HQ=; b=hCFUxBVv/ZUMQCWrCAnZ1njtirp2xU3U6SBPWCg4hAkfF3qLKzylRirt utFmyDlnjpnJtVdpuVK80z/etcEkTqHh5yLVBtjtmabPlVoy5GYmtWv6U 9YjMm5BSeciclmd339NOx6KB40payHbQYS++JsNgYO1w56YKHoIQai0EZ GIVNS+0eU3ywmopta/Z/PSQynaraAhesVmecKE4HOdHHQD7whV+hLQhC1 XIeXFpC0qWvDnZ4d+iYG2dMK6vG/RKy94qgt1he07hwMoD6mXY0nFD2Xa tJGkXqW8pC2HMUeI37Nu/ZbuwKRT8/88uUEL4Te2+f/D+aGxHd17CMCF4 Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10825"; a="463461967" X-IronPort-AV: E=Sophos;i="6.02,232,1688454000"; d="scan'208";a="463461967" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Sep 2023 07:48:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10825"; a="776642531" X-IronPort-AV: E=Sophos;i="6.02,232,1688454000"; d="scan'208";a="776642531" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga001.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Sep 2023 07:48:49 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1qdtpl-006y2X-2X; Wed, 06 Sep 2023 17:48:45 +0300 Date: Wed, 6 Sep 2023 17:48:45 +0300 From: Andy Shevchenko To: Bartosz Golaszewski Cc: Aaro Koskinen , Janusz Krzysztofik , Tony Lindgren , Russell King , Mika Westerberg , Linus Walleij , Dipen Patel , Thierry Reding , Jonathan Hunter , Hans de Goede , Mark Gross , linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org, timestamp@lists.linux.dev, linux-tegra@vger.kernel.org, platform-driver-x86@vger.kernel.org, Bartosz Golaszewski Subject: Re: [RFT PATCH 15/21] arm: omap1: ams-delta: stop using gpiochip_find() Message-ID: References: <20230905185309.131295-1-brgl@bgdev.pl> <20230905185309.131295-16-brgl@bgdev.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230905185309.131295-16-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 Tue, Sep 05, 2023 at 08:53:03PM +0200, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > gpiochip_find() is going away as it's not hot-unplug safe. This platform > is not affected by any of the related problems as this GPIO controller > cannot really go away but in order to finally remove this function, we > need to convert it to using gpio_device_find() as well. Side question, have you used --patience when preparing this series? -- With Best Regards, Andy Shevchenko