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 16C11C433F5 for ; Mon, 16 May 2022 13:20:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236549AbiEPNUA (ORCPT ); Mon, 16 May 2022 09:20:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42442 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232120AbiEPNT4 (ORCPT ); Mon, 16 May 2022 09:19:56 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3927925C41 for ; Mon, 16 May 2022 06:19:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1652707195; x=1684243195; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=RTPbt/pEUPHzGxjnN3iB9RlXzJDpAPf83MfU550iqPo=; b=FK8S2vvlruwHglboCu+XDYdJBpD/ReN0Gv1JF3Umedx1guSBiwaMV46m fUhxhMo82m/E9VvEU/vvRMRqrv2AOuPPME7WXCouFy5ZkupIt1Sn9j7Jm tFXwFFcQMflvPzfFyLSSF956qsO9Ka/dUaKl9a+nqIWYo83Fi7JKa9ft0 qFHZGqVjbvwpBMbmS9yQpl9hyuQrMmpecWRz3TUCcLgxkdO3h0vh3OvLl gTx3Ou0LszEqWtSHRjfpV1Uzs354BZwPXzO8Y29EKph0XLiAPECykjRhz iw4M2rMHy+2/gf0BQ2PkTT8TjKX2LeA9tLDTB2BWif0YIcLepo0UvvlPg A==; X-IronPort-AV: E=McAfee;i="6400,9594,10348"; a="333885186" X-IronPort-AV: E=Sophos;i="5.91,229,1647327600"; d="scan'208";a="333885186" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 May 2022 06:19:54 -0700 X-IronPort-AV: E=Sophos;i="5.91,229,1647327600"; d="scan'208";a="568314949" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.162]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 May 2022 06:19:50 -0700 Received: by lahna (sSMTP sendmail emulation); Mon, 16 May 2022 16:19:46 +0300 Date: Mon, 16 May 2022 16:19:46 +0300 From: Mika Westerberg To: Gil Fine Cc: andreas.noever@gmail.com, michael.jamet@intel.com, YehezkelShB@gmail.com, linux-usb@vger.kernel.org, lukas@wunner.de Subject: Re: [PATCH v3 6/6] thunderbolt: Change TMU mode to HiFi uni-directional once DisplayPort tunneled Message-ID: References: <20220511140549.10571-1-gil.fine@intel.com> <20220511140549.10571-7-gil.fine@intel.com> <20220515202746.GA8368@ccdjLinux26> <20220516085903.GC8368@ccdjLinux26> <20220516132141.GE8368@ccdjLinux26> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220516132141.GE8368@ccdjLinux26> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org Hi Gil, On Mon, May 16, 2022 at 04:21:41PM +0300, Gil Fine wrote: > > So instead I suggest to put the device_for_each_child() in tmu.c and > > then the tb_switch_tmu_config_enable() static right above it. Please > > also name the resulting API function consistently. > > OK, got you and fixed that. > Please let me know when you think that I can send out the v4 series. You can send it whenever you want but I think it can go to v5.20 and not v5.19 since I was planning to send out my pull request for Greg tomorrow. I can pick it up after v5.19-rc1 is released.