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 2A824C41513 for ; Fri, 4 Aug 2023 14:50:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230504AbjHDOu4 (ORCPT ); Fri, 4 Aug 2023 10:50:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36892 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231847AbjHDOuy (ORCPT ); Fri, 4 Aug 2023 10:50:54 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1936649E1; Fri, 4 Aug 2023 07:50:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1691160652; x=1722696652; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=40OHL2z1D2BDju0OQCJozvDlO1ndY6wr+lQO9kmgHxY=; b=Wm0g//ikntRf63tOCAUT/3qzX+bp7Uk5BAYRhTfO4U5ygi7Tas6PcIbh AJZD+bgQIX6dHkNusokC50xiK5tslYApGoARkCSFvQJyfXG0mimIQ75vH gIexQt4/6Qh/XyvjCl8KNE91Ol+nkKD32R/jBWy8Eiv0FfG2r/CDXB+Dy 1qH9CjWF5umlWtSbh8wHpLU3meZO5t2rCsFwT4s03bDbnpc3h8UW4booq cNRIB9Dm4C2BzoZ/a+noMW/TbngGMDesTCbwmGTyJueiEE451p/QQTmFP U7GHMNn6Z3IExegn1gzl3BOC2lCAM4bVs6ig9czWrg+aDApzaFSAE9Oi9 Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10792"; a="367630428" X-IronPort-AV: E=Sophos;i="6.01,255,1684825200"; d="scan'208";a="367630428" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Aug 2023 07:50:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10792"; a="820150960" X-IronPort-AV: E=Sophos;i="6.01,255,1684825200"; d="scan'208";a="820150960" Received: from smile.fi.intel.com ([10.237.72.54]) by FMSMGA003.fm.intel.com with ESMTP; 04 Aug 2023 07:50:48 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1qRw8c-00Cz83-2p; Fri, 04 Aug 2023 17:50:46 +0300 Date: Fri, 4 Aug 2023 17:50:46 +0300 From: Andy Shevchenko To: Biju Das Cc: Wolfram Sang , linux-i2c@vger.kernel.org, Geert Uytterhoeven , Dmitry Torokhov , Andi Shyti , Alexandre Belloni , Jonathan Cameron , linux-rtc@vger.kernel.org, linux-iio@vger.kernel.org, linux-renesas-soc@vger.kernel.org Subject: Re: [PATCH v6 3/4] i2c: Enhance i2c_get_match_data() Message-ID: References: <20230804070915.117829-1-biju.das.jz@bp.renesas.com> <20230804070915.117829-4-biju.das.jz@bp.renesas.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230804070915.117829-4-biju.das.jz@bp.renesas.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 Fri, Aug 04, 2023 at 08:09:14AM +0100, Biju Das wrote: > Enhance i2c_get_match_data() for a faster path for device_get_ > match_data(). Strange wrap, the function name shouldn't have a new line in between :-) > While at it, add const to struct i2c_driver to prevent overriding > the driver pointer. ... > v6: > * Separate patch to prepare for better difference for > i2c_match_id() changes. With this it actually should be patch 2 and patch 2 become 3 (there is not much difference code wise, but logically this can be applied even without the rest). With the above addressed Reviewed-by: Andy Shevchenko -- With Best Regards, Andy Shevchenko