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 3B0B5C433FE for ; Wed, 2 Nov 2022 11:01:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229988AbiKBLBk (ORCPT ); Wed, 2 Nov 2022 07:01:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46150 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229513AbiKBLBj (ORCPT ); Wed, 2 Nov 2022 07:01:39 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D541029361; Wed, 2 Nov 2022 04:01:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1667386897; x=1698922897; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=d5QvCOMsjMBr33OdD5oCaZxykkRV0ETIs7RVP9U9RZc=; b=UquZEJQ7H6BK2r+Bsm7LS5BcgU58r4roA2OV50tbrv9S88Sc2gqjL2Iz d3zNyRMFJQlg2TqHVi4GxqEy0mbYoTdsPnYj9c8L+FCUTJNpy+b3nHFDX rkpmg2HHNtDg4W9ByQkbzTLWbwHFBa4N/T4/mpmciQIk8rat08gcGDMOa jXbwh7+INY+JLEfY6OKYLYWKc/40zb8xAYZzxSz108RQymJAWBytQlDXx LEHaYjpzmFrO85zmIoJshh8hgnuLN1pi+AOYMoQAEXF6GTSmqUCAjDRl2 GwvFiVsYGhEUIDfy0nSVz+6wFWiLB/+6K7JvaXK3KDIXmso7HLuI8jqzi Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10518"; a="336054732" X-IronPort-AV: E=Sophos;i="5.95,232,1661842800"; d="scan'208";a="336054732" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Nov 2022 04:01:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10518"; a="634222033" X-IronPort-AV: E=Sophos;i="5.95,232,1661842800"; d="scan'208";a="634222033" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga002.jf.intel.com with ESMTP; 02 Nov 2022 04:01:33 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oqBUx-0068pG-1t; Wed, 02 Nov 2022 13:01:31 +0200 Date: Wed, 2 Nov 2022 13:01:31 +0200 From: Andy Shevchenko To: linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Cc: Qiang Zhao , Li Yang , Daniel Scally , Heikki Krogerus , Sakari Ailus Subject: Re: [PATCH v2 0/2] gpiolib: more cleanups to get rid of of_node Message-ID: References: <20221005152947.71696-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-acpi@vger.kernel.org On Fri, Oct 21, 2022 at 10:01:34PM +0300, Andy Shevchenko wrote: > On Wed, Oct 05, 2022 at 06:29:45PM +0300, Andy Shevchenko wrote: > > One more user outside of GPIO library and pin control folders needs > > to be updated to use fwnode instead of of_node. To make this easier > > introduce a helper in property.h and convert the user. > > > > Note, the helper will be useful not only for the current users, > > but any future ones that want to replace of_device_is_compatible() > > with analogous fwnode API. > > > > Changelog v2: > > - placed new helper correctly in the property.h > > Any comments on the series? I'm going to apply this to my branch with Sakari's tag since there is no answer from PPC maintainers for a month. -- With Best Regards, Andy Shevchenko