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 41BEFC4708D for ; Wed, 4 Jan 2023 16:56:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239995AbjADQ4B (ORCPT ); Wed, 4 Jan 2023 11:56:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51598 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240020AbjADQzj (ORCPT ); Wed, 4 Jan 2023 11:55:39 -0500 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AA2923FC90; Wed, 4 Jan 2023 08:51:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1672851102; x=1704387102; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=BQzAaG/riItgL7XH8d4hpWwMRvqYPpCa+e8ZrSNpK3A=; b=WhRn8OVtYTz5pNxKNytEem8OJ7QcSaEzX1sMnuIn8pY6ysGyH9LuO8b1 VPa+IqfpzsnUgwem+8tXgKWgLKv02raR9FWs00/EMLkfK7s3YufQJrWpi iL5vitwJ1YbVZwlcXYN/gK6qUeXumG1r8uGUMUoMNdStZm5GcGJtCGto8 qCQM8+hh6xtSsLP8qsBUyDLXeTvhYKsSxoRjxkVejYd7hMaRNGdR2M55i SVON/jBxj0Dz5DaTen4eibMS/IeZA46J5BCd+ch7te+YemqrpxGxINibI 6odABoLk4+h4MYBzm9Ewz4oHPhjJsIjTmKtNBTBZqqilob0ZjBB0PDPh9 w==; X-IronPort-AV: E=McAfee;i="6500,9779,10580"; a="305485208" X-IronPort-AV: E=Sophos;i="5.96,300,1665471600"; d="scan'208";a="305485208" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jan 2023 08:51:29 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10580"; a="718509909" X-IronPort-AV: E=Sophos;i="5.96,300,1665471600"; d="scan'208";a="718509909" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga008.fm.intel.com with ESMTP; 04 Jan 2023 08:51:26 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1pD6z7-004Nww-0l; Wed, 04 Jan 2023 18:51:25 +0200 Date: Wed, 4 Jan 2023 18:51:24 +0200 From: Andy Shevchenko To: Thierry Reding Cc: Dmitry Torokhov , Bartosz Golaszewski , Linus Walleij , linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, Mika Westerberg , Bartosz Golaszewski , Thierry Reding Subject: Re: [rft, PATCH v4 0/3] gpiolib: eventual of_node retirement Message-ID: References: <20221228092045.80425-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Wed, Jan 04, 2023 at 05:41:46PM +0100, Thierry Reding wrote: > On Wed, Dec 28, 2022 at 11:20:42AM +0200, Andy Shevchenko wrote: > > Now that all GPIO library users are converted to use fwnode, > > Drop redundant field from struct gpio_chip and accompanying > > code. > > > > Bart, I prefer this series to go as soon as possible if you > > have no objection. Or even as v6.2 material. > > > > Thierry, can you please test it once again, so we will be sure > > there is no breakage for OF platforms? > > Seems to be working fine on at least Jetson TX1, so: > > Tested-by: Thierry Reding Thank you and HNY! -- With Best Regards, Andy Shevchenko