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 2C6F0C4332F for ; Mon, 21 Feb 2022 17:55:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229973AbiBURzd (ORCPT ); Mon, 21 Feb 2022 12:55:33 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:47182 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230491AbiBURxW (ORCPT ); Mon, 21 Feb 2022 12:53:22 -0500 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5B32FDEEB; Mon, 21 Feb 2022 09:48:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645465738; x=1677001738; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=zwiNRlhLeWQqN35/KdrWsXpG2B+PLJoioW20hr3nYM4=; b=Fpj6r1A0icBVFRchNGO1e+H1iS37obos0vdGnmhX9q/wYCFMcAwBlGUV z4h5n+FpGvqCHbsc1dsVexNhdj02ZvolJ4/cvi/W11q3fIpJM6ojqGryz ZTA6Q5ZPmB/4NzaWXkSCL2vlI+4p0NKoQ6q/nBMjDwAI7gpt/e9Ii3O53 Tiwso0TRkuAwPZPJj0AsJCggvnOjEiNnkcPUkIN1HIMphaaLZm23AeeMi c2ekN99W7mp+X5hFxhpoSI0gpm/2hc6KDPuotb/0ysLk3tVQIKqScLwYp rUNHmXwvIXlesGH5enw4pg2bBxVd/ywRIqybKOKl+KFNrdirgzY1t0nuL A==; X-IronPort-AV: E=McAfee;i="6200,9189,10265"; a="251732801" X-IronPort-AV: E=Sophos;i="5.88,386,1635231600"; d="scan'208";a="251732801" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2022 09:48:57 -0800 X-IronPort-AV: E=Sophos;i="5.88,386,1635231600"; d="scan'208";a="507704887" Received: from smile.fi.intel.com ([10.237.72.59]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2022 09:48:53 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nMCn2-006s1L-U8; Mon, 21 Feb 2022 19:48:00 +0200 Date: Mon, 21 Feb 2022 19:48:00 +0200 From: Andy Shevchenko To: =?iso-8859-1?Q?Cl=E9ment_L=E9ger?= Cc: Daniel Scally , Heikki Krogerus , Sakari Ailus , Greg Kroah-Hartman , "Rafael J . Wysocki" , Wolfram Sang , Peter Rosin , Russell King , Andrew Lunn , Heiner Kallweit , "David S . Miller" , Jakub Kicinski , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org, netdev@vger.kernel.org, Thomas Petazzoni , Alexandre Belloni Subject: Re: [RFC 03/10] base: swnode: use fwnode_get_match_data() Message-ID: References: <20220221162652.103834-1-clement.leger@bootlin.com> <20220221162652.103834-4-clement.leger@bootlin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220221162652.103834-4-clement.leger@bootlin.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-i2c@vger.kernel.org On Mon, Feb 21, 2022 at 05:26:45PM +0100, Clément Léger wrote: > In order to allow matching devices with software node with > device_get_match_data(), use fwnode_get_match_data() for > .device_get_match_data operation. ... > + .device_get_match_data = fwnode_get_match_data, Huh? It should be other way around, no? I mean that each of the resource providers may (or may not) provide a method for the specific fwnode abstraction. -- With Best Regards, Andy Shevchenko